Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Target Management » Hanging while connecting to daemon
Hanging while connecting to daemon [message #21564] Mon, 21 April 2008 17:47 Go to next message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
I am using 2.0.3. I have been successfully connecting "userID1" to the
daemon for a while now. But when I try to connect "userID2" to the daemon
server running on AIX, it just hangs with Connect (0%) in the lower right
corner. I see some processes running on the AIX box that never appear to
return.

userID2 999626 1040576 0 13:28:43 pts/144 0:00 -ksh -c
/usr/java14/jre/bin/java -cp
/opt/rseserver:/opt/rseserver/dstore_extra_server.jar:/opt/r seserver/dstore_core.jar:/opt/rseserver/dstore_miners.jar:/o pt/rseserver/clientserver.jar
-DA_PLUGIN_PATH=/opt/rseserver/ -DDSTORE_SPIRIT_ON=true
org.eclipse.dstore.core.server.Server 12200-12203 120000 1208798923525
root 1040576 881520 0 13:28:43 pts/144 0:00 perl
/opt/rseserver//auth.pl userID2 /opt/rseserver/ 12200-12203 120000
1208798923525 /usr/java14/jre
root 881520 1082214 0 13:26:51 pts/144 0:00 java
-DA_PLUGIN_PATH=/opt/rseserver/ -DDSTORE_TRACING_ON=false
org.eclipse.dstore.core.server.ServerLauncher 4075 12200-12203

If I kill the daemon and processes on the AIX box, RSE then returns for
"userID2" to tell me that it Failed to connect to the daemon with an
unexpected exception.

java.net.ConnectException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSock et(Unknown
Source)
at
org.eclipse.dstore.core.client.ClientConnection.connectDaemo n(ClientConnection.java:739)
at
org.eclipse.dstore.core.client.ClientConnection.launchServer (ClientConnection.java:642)
at
org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.launchServer(DStoreConnectorService.java:1225)
at
org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.launchServer(DStoreConnectorService.java:1215)
at
org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.internalConnect(DStoreConnectorService.java:637)
at
org.eclipse.rse.core.subsystems.AbstractConnectorService.con nect(AbstractConnectorService.java:412)
at org.eclipse.rse.core.subsystems.SubSystem.connect(SubSystem. java:2255)
at
org.eclipse.rse.internal.ui.actions.SystemConnectAllSubSyste msAction$ConnectAllJob.run(SystemConnectAllSubSystemsAction. java:69)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Has anyone seen this issue before? I'm not sure what could be different
between the connections for "userID1" vs "userID2". I've tried connecting
both user IDs at the same time as well as individually. I have tried
"userID2" connecting with REXEC or to a running server and both of those
work fine. I just doesn't work connecting to the daemon. Thanks for any
help.
Re: Hanging while connecting to daemon [message #21611 is a reply to message #21564] Mon, 21 April 2008 17:57 Go to previous messageGo to next message
David McKnight is currently offline David McKnight
Messages: 244
Registered: July 2009
Senior Member
One possible difference could be the user profiles. When a user connects to
the daemon, a server is launched via a shell launched for that user. The
profile for the user will be executed when the shell is started. Could user
2 be setup to use a different jvm than user 1?

dave


"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:30b0e7d6912aa41fd4d430e097325ac9$1@www.eclipse.org...
>I am using 2.0.3. I have been successfully connecting "userID1" to the
>daemon for a while now. But when I try to connect "userID2" to the daemon
>server running on AIX, it just hangs with Connect (0%) in the lower right
>corner. I see some processes running on the AIX box that never appear to
>return.
>
> userID2 999626 1040576 0 13:28:43 pts/144 0:00 -ksh -c
> /usr/java14/jre/bin/java -cp
> /opt/rseserver:/opt/rseserver/dstore_extra_server.jar:/opt/r seserver/dstore_core.jar:/opt/rseserver/dstore_miners.jar:/o pt/rseserver/clientserver.jar
> -DA_PLUGIN_PATH=/opt/rseserver/ -DDSTORE_SPIRIT_ON=true
> org.eclipse.dstore.core.server.Server 12200-12203 120000 1208798923525
> root 1040576 881520 0 13:28:43 pts/144 0:00 perl
> /opt/rseserver//auth.pl userID2 /opt/rseserver/ 12200-12203 120000
> 1208798923525 /usr/java14/jre root 881520 1082214 0 13:26:51 pts/144
> 0:00 java -DA_PLUGIN_PATH=/opt/rseserver/ -DDSTORE_TRACING_ON=false
> org.eclipse.dstore.core.server.ServerLauncher 4075 12200-12203
> If I kill the daemon and processes on the AIX box, RSE then returns for
> "userID2" to tell me that it Failed to connect to the daemon with an
> unexpected exception.
>
> java.net.ConnectException: Connection refused: connect
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source)
> at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSock et(Unknown
> Source)
> at
> org.eclipse.dstore.core.client.ClientConnection.connectDaemo n(ClientConnection.java:739)
> at
> org.eclipse.dstore.core.client.ClientConnection.launchServer (ClientConnection.java:642)
> at
> org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.launchServer(DStoreConnectorService.java:1225)
> at
> org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.launchServer(DStoreConnectorService.java:1215)
> at
> org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.internalConnect(DStoreConnectorService.java:637)
> at
> org.eclipse.rse.core.subsystems.AbstractConnectorService.con nect(AbstractConnectorService.java:412)
> at org.eclipse.rse.core.subsystems.SubSystem.connect(SubSystem. java:2255)
> at
> org.eclipse.rse.internal.ui.actions.SystemConnectAllSubSyste msAction$ConnectAllJob.run(SystemConnectAllSubSystemsAction. java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
> Has anyone seen this issue before? I'm not sure what could be different
> between the connections for "userID1" vs "userID2". I've tried connecting
> both user IDs at the same time as well as individually. I have tried
> "userID2" connecting with REXEC or to a running server and both of those
> work fine. I just doesn't work connecting to the daemon. Thanks for any
> help.
>
>
>
>
Re: Hanging while connecting to daemon [message #21656 is a reply to message #21611] Mon, 21 April 2008 18:13 Go to previous messageGo to next message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
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 #21744 is a reply to message #21656] Mon, 21 April 2008 19:13 Go to previous messageGo to next message
David McKnight is currently offline 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 #21790 is a reply to message #21744] Mon, 21 April 2008 20:48 Go to previous messageGo to next message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
OK, given that, is there a recommendation for how many server ports would
be considered sufficient to handle 500-600 clients? Currently the Daemon
runs on 4075 and our firewall guys are asking how many of these additional
server ports we need. Our security folks get very twitchy about opening
up large blocks of ports so we'd like the range to be minimal if possible.
Any guidance you could give is appreciated.

Thanks
Re: Hanging while connecting to daemon [message #21922 is a reply to message #21790] Tue, 22 April 2008 14:43 Go to previous messageGo to next message
David McKnight is currently offline David McKnight
Messages: 244
Registered: July 2009
Senior Member
Hi Denise,

I don't have much experience with a large number of clients on a single
server like that so I don't have a good suggestion on the number of ports to
supply. One thing you may want to keep in mind with that many clients on
one machine is the heavy memory consumption with all the JVMs running. For
such scenarios, some IBM teams are using dstore as a single process server
that creates a thread for each client along with security hooks. In order
to support that kind of model, you would need your own daemon process and
your own ISystemService to provide thead-level security.


"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:1c6856f460b5fcb77d10585166adfd4b$1@www.eclipse.org...
> OK, given that, is there a recommendation for how many server ports would
> be considered sufficient to handle 500-600 clients? Currently the Daemon
> runs on 4075 and our firewall guys are asking how many of these additional
> server ports we need. Our security folks get very twitchy about opening
> up large blocks of ports so we'd like the range to be minimal if possible.
> Any guidance you could give is appreciated.
>
> Thanks
>
Re: Hanging while connecting to daemon [message #22098 is a reply to message #21922] Tue, 22 April 2008 20:04 Go to previous messageGo to next message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
I've been going back and forth with our network guys about this. I
believe 500-600 is an big overestimate by them but I could reasonably see
it being around 100. Is there a way to determine how many server ports
may need to be used for 100-150 clients short of trying to connect that
many users? I could do some analysis with a much smaller number of users
but I'm not sure how to scale that up. Is there a defined limit somewhere
to the number of clients that can use a single port? I'm not sure if RSE
can/does specify some limit or if I should investigate elsewhere for a
limit.

As for the memory consumption, that is something we did not consider so
thanks for the heads up. I hope we don't have to do what you mention IBM
does as I imagine I'd have tons more questions in order to figure out to
implement it :)

Thanks!
Re: Hanging while connecting to daemon [message #22142 is a reply to message #22098] Tue, 22 April 2008 20:59 Go to previous message
David McKnight is currently offline David McKnight
Messages: 244
Registered: July 2009
Senior Member
I talked to a couple of those product teams today and they told me they'll
get back to me on what they set for their port ranges. The reason you need
more than one is because multiple clients may attempt to connect at the same
time (requiring multiple sockets to wait for connect). The higher the
number of users, the more likely it is that two connects will happen at the
same time.

As for the memory stuff, I know things are working okay with around 300
clients to the same server but the single-process model should be better for
performance and memory especialy when the number of clients is large.


"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:f226e5a6f7fa6a88ba544a05eeb42c7e$1@www.eclipse.org...
> I've been going back and forth with our network guys about this. I
> believe 500-600 is an big overestimate by them but I could reasonably see
> it being around 100. Is there a way to determine how many server ports
> may need to be used for 100-150 clients short of trying to connect that
> many users? I could do some analysis with a much smaller number of users
> but I'm not sure how to scale that up. Is there a defined limit somewhere
> to the number of clients that can use a single port? I'm not sure if RSE
> can/does specify some limit or if I should investigate elsewhere for a
> limit.
>
> As for the memory consumption, that is something we did not consider so
> thanks for the heads up. I hope we don't have to do what you mention IBM
> does as I imagine I'd have tons more questions in order to figure out to
> implement it :)
>
> Thanks!
>
>
Re: Hanging while connecting to daemon [message #573890 is a reply to message #21564] Mon, 21 April 2008 17:57 Go to previous message
David McKnight is currently offline David McKnight
Messages: 244
Registered: July 2009
Senior Member
One possible difference could be the user profiles. When a user connects to
the daemon, a server is launched via a shell launched for that user. The
profile for the user will be executed when the shell is started. Could user
2 be setup to use a different jvm than user 1?

dave


"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:30b0e7d6912aa41fd4d430e097325ac9$1@www.eclipse.org...
>I am using 2.0.3. I have been successfully connecting "userID1" to the
>daemon for a while now. But when I try to connect "userID2" to the daemon
>server running on AIX, it just hangs with Connect (0%) in the lower right
>corner. I see some processes running on the AIX box that never appear to
>return.
>
> userID2 999626 1040576 0 13:28:43 pts/144 0:00 -ksh -c
> /usr/java14/jre/bin/java -cp
> /opt/rseserver:/opt/rseserver/dstore_extra_server.jar:/opt/r seserver/dstore_core.jar:/opt/rseserver/dstore_miners.jar:/o pt/rseserver/clientserver.jar
> -DA_PLUGIN_PATH=/opt/rseserver/ -DDSTORE_SPIRIT_ON=true
> org.eclipse.dstore.core.server.Server 12200-12203 120000 1208798923525
> root 1040576 881520 0 13:28:43 pts/144 0:00 perl
> /opt/rseserver//auth.pl userID2 /opt/rseserver/ 12200-12203 120000
> 1208798923525 /usr/java14/jre root 881520 1082214 0 13:26:51 pts/144
> 0:00 java -DA_PLUGIN_PATH=/opt/rseserver/ -DDSTORE_TRACING_ON=false
> org.eclipse.dstore.core.server.ServerLauncher 4075 12200-12203
> If I kill the daemon and processes on the AIX box, RSE then returns for
> "userID2" to tell me that it Failed to connect to the daemon with an
> unexpected exception.
>
> java.net.ConnectException: Connection refused: connect
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
> at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source)
> at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSock et(Unknown
> Source)
> at
> org.eclipse.dstore.core.client.ClientConnection.connectDaemo n(ClientConnection.java:739)
> at
> org.eclipse.dstore.core.client.ClientConnection.launchServer (ClientConnection.java:642)
> at
> org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.launchServer(DStoreConnectorService.java:1225)
> at
> org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.launchServer(DStoreConnectorService.java:1215)
> at
> org.eclipse.rse.connectorservice.dstore.DStoreConnectorServi ce.internalConnect(DStoreConnectorService.java:637)
> at
> org.eclipse.rse.core.subsystems.AbstractConnectorService.con nect(AbstractConnectorService.java:412)
> at org.eclipse.rse.core.subsystems.SubSystem.connect(SubSystem. java:2255)
> at
> org.eclipse.rse.internal.ui.actions.SystemConnectAllSubSyste msAction$ConnectAllJob.run(SystemConnectAllSubSystemsAction. java:69)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
> Has anyone seen this issue before? I'm not sure what could be different
> between the connections for "userID1" vs "userID2". I've tried connecting
> both user IDs at the same time as well as individually. I have tried
> "userID2" connecting with REXEC or to a running server and both of those
> work fine. I just doesn't work connecting to the daemon. Thanks for any
> help.
>
>
>
>
Re: Hanging while connecting to daemon [message #573907 is a reply to message #21611] Mon, 21 April 2008 18:13 Go to previous message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
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 Go to previous message
David McKnight is currently offline 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 #573984 is a reply to message #21744] Mon, 21 April 2008 20:48 Go to previous message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
OK, given that, is there a recommendation for how many server ports would
be considered sufficient to handle 500-600 clients? Currently the Daemon
runs on 4075 and our firewall guys are asking how many of these additional
server ports we need. Our security folks get very twitchy about opening
up large blocks of ports so we'd like the range to be minimal if possible.
Any guidance you could give is appreciated.

Thanks
Re: Hanging while connecting to daemon [message #574074 is a reply to message #21790] Tue, 22 April 2008 14:43 Go to previous message
David McKnight is currently offline David McKnight
Messages: 244
Registered: July 2009
Senior Member
Hi Denise,

I don't have much experience with a large number of clients on a single
server like that so I don't have a good suggestion on the number of ports to
supply. One thing you may want to keep in mind with that many clients on
one machine is the heavy memory consumption with all the JVMs running. For
such scenarios, some IBM teams are using dstore as a single process server
that creates a thread for each client along with security hooks. In order
to support that kind of model, you would need your own daemon process and
your own ISystemService to provide thead-level security.


"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:1c6856f460b5fcb77d10585166adfd4b$1@www.eclipse.org...
> OK, given that, is there a recommendation for how many server ports would
> be considered sufficient to handle 500-600 clients? Currently the Daemon
> runs on 4075 and our firewall guys are asking how many of these additional
> server ports we need. Our security folks get very twitchy about opening
> up large blocks of ports so we'd like the range to be minimal if possible.
> Any guidance you could give is appreciated.
>
> Thanks
>
Re: Hanging while connecting to daemon [message #574171 is a reply to message #21922] Tue, 22 April 2008 20:04 Go to previous message
Denise Schmidt is currently offline Denise Schmidt
Messages: 66
Registered: July 2009
Member
I've been going back and forth with our network guys about this. I
believe 500-600 is an big overestimate by them but I could reasonably see
it being around 100. Is there a way to determine how many server ports
may need to be used for 100-150 clients short of trying to connect that
many users? I could do some analysis with a much smaller number of users
but I'm not sure how to scale that up. Is there a defined limit somewhere
to the number of clients that can use a single port? I'm not sure if RSE
can/does specify some limit or if I should investigate elsewhere for a
limit.

As for the memory consumption, that is something we did not consider so
thanks for the heads up. I hope we don't have to do what you mention IBM
does as I imagine I'd have tons more questions in order to figure out to
implement it :)

Thanks!
Re: Hanging while connecting to daemon [message #574182 is a reply to message #22098] Tue, 22 April 2008 20:59 Go to previous message
David McKnight is currently offline David McKnight
Messages: 244
Registered: July 2009
Senior Member
I talked to a couple of those product teams today and they told me they'll
get back to me on what they set for their port ranges. The reason you need
more than one is because multiple clients may attempt to connect at the same
time (requiring multiple sockets to wait for connect). The higher the
number of users, the more likely it is that two connects will happen at the
same time.

As for the memory stuff, I know things are working okay with around 300
clients to the same server but the single-process model should be better for
performance and memory especialy when the number of clients is large.


"Denise Schmidt" <denise.schmidt@lmco.com> wrote in message
news:f226e5a6f7fa6a88ba544a05eeb42c7e$1@www.eclipse.org...
> I've been going back and forth with our network guys about this. I
> believe 500-600 is an big overestimate by them but I could reasonably see
> it being around 100. Is there a way to determine how many server ports
> may need to be used for 100-150 clients short of trying to connect that
> many users? I could do some analysis with a much smaller number of users
> but I'm not sure how to scale that up. Is there a defined limit somewhere
> to the number of clients that can use a single port? I'm not sure if RSE
> can/does specify some limit or if I should investigate elsewhere for a
> limit.
>
> As for the memory consumption, that is something we did not consider so
> thanks for the heads up. I hope we don't have to do what you mention IBM
> does as I imagine I'd have tons more questions in order to figure out to
> implement it :)
>
> Thanks!
>
>
Previous Topic:Re: rse; dstore connector service; using port 0 error
Next Topic:programmatic creation of dynamic filters in Remote System view
Goto Forum:
  


Current Time: Fri Oct 24 11:20:05 GMT 2014

Powered by FUDForum. Page generated in 0.27716 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software