Re: RSE communications daemon could not be started onport4300

Okay that solves that problem. I have WDSC set to start automatically
when I log on so it was taking that port, I guess.

I have not yet made the switch over to RDi yet. It keeps messing up my
workspace converting it to RDi format and then losing most of my
settings and options.

I use it occasionally.

Thanks, Matt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of DeLong, Eric
Sent: Monday, February 08, 2010 3:18 PM
To: Rational Developer for IBM i / Websphere Development Studio
ClientforSystem i & iSeries
Subject: Re: [WDSCI-L] RSE communications daemon could not be started
onport4300

I used to get this when trying to run WDSC and Rdi at the same time.
The first client launched got a good socket connection to port 4300. I
also used to get this when connecting through a SSL proxy. In this
case, the Rdi client had to be launched before starting the SSL proxy.

Hth,
-Eric DeLong

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tyler, Matt
Sent: Monday, February 08, 2010 2:43 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: [WDSCI-L] RSE communications daemon could not be started on
port4300

I keep getting this error message when running "stuff" in RDi, like the
Application Diagrams or the Outline.



NETSTAT does not specifically identify the port being busy.



Anyone have an idea what to fix?

The RSE communications daemon could not be started on port 4300. Check
that the port is free and restart the daemon or change the port used by
the daemon using the Remote Systems -> Communications Workbench
preference page.

<



Thanks, Matt