|
|
|
Re: Hanging while connecting to daemon [message #21744 is a reply to message #21656] |
Mon, 21 April 2008 19:13 |
David McKnight Messages: 244 Registered: July 2009 |
Senior Member |
|
|
Hi Denise,
The port range specified for the server is required because a particular
port may already be waiting to accept a connection. You can use the same
port for multiple connections, there can't be two sockets accepting
connections on that port at the same time.
For example,
You launch the daemon like this: daemon.pl 7000 7000-70005 (where 7000-7005
is the server port range):
Client 1 connects: Port 7000 is busy accepting clients so the server can't
be started with 7000. Instead it may start with 7001.
Client 2 connects: Port 7000 is busy, and although Client 1 is connected on
port 7001, Client 2 can still use it because 7001 is not busy accepting.
Dave
"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:c1be1c6fb581e4c5f686179c12fc707a$1@www.eclipse.org...
> Thank you so much. I figured it would be something I was just
> overlooking. When you asked about the profiles, I realized that "userID2"
> profile just might prompt for user input and sure enough, that was the
> problem. I'm glad it was something simple. Thanks!
>
> I do have a follow up question though. When multiple clients connect, do
> they all use the same port from the serverportrange provided to the daemon
> on startup or does each client get a different port? I connected from my
> workstation as "userID1" and "userID2" and they both launched new servers
> on the same port. I also tried previous to connect "userID1" from 2
> different workstations and they also launched servers on the same port.
> If all the clients use the same port, why would I want to define a
> serverportrange instead of just one port? Thanks much.
>
|
|
|
|
|
|
|
|
|
Re: Hanging while connecting to daemon [message #573953 is a reply to message #21656] |
Mon, 21 April 2008 19:13 |
David McKnight Messages: 244 Registered: July 2009 |
Senior Member |
|
|
Hi Denise,
The port range specified for the server is required because a particular
port may already be waiting to accept a connection. You can use the same
port for multiple connections, there can't be two sockets accepting
connections on that port at the same time.
For example,
You launch the daemon like this: daemon.pl 7000 7000-70005 (where 7000-7005
is the server port range):
Client 1 connects: Port 7000 is busy accepting clients so the server can't
be started with 7000. Instead it may start with 7001.
Client 2 connects: Port 7000 is busy, and although Client 1 is connected on
port 7001, Client 2 can still use it because 7001 is not busy accepting.
Dave
"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:c1be1c6fb581e4c5f686179c12fc707a$1@www.eclipse.org...
> Thank you so much. I figured it would be something I was just
> overlooking. When you asked about the profiles, I realized that "userID2"
> profile just might prompt for user input and sure enough, that was the
> problem. I'm glad it was something simple. Thanks!
>
> I do have a follow up question though. When multiple clients connect, do
> they all use the same port from the serverportrange provided to the daemon
> on startup or does each client get a different port? I connected from my
> workstation as "userID1" and "userID2" and they both launched new servers
> on the same port. I also tried previous to connect "userID1" from 2
> different workstations and they also launched servers on the same port.
> If all the clients use the same port, why would I want to define a
> serverportrange instead of just one port? Thanks much.
>
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02086 seconds