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 #573851] Mon, 21 April 2008 17:47
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.
Previous Topic:programmatic creation of dynamic filters
Next Topic:Set daemon port programmatically
Goto Forum:
  


Current Time: Wed Oct 22 05:00:55 GMT 2014

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

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