Client gui hangs

[Daniel Lee]

I’m running Qdxi5.4 REV 1 on AIX 5.2 and our client is on Windows XP.  When I run the TPS testing tool from my client gui the GUI hangs.  Another co-worker here can run it fine from his workstation and he’s using the same OS as I am.

After haging for around 5 min. the tps tester returns no output but I get the following in the server.log file complainging about my workstation’s IP address:  (I substituted XXX.XX.XX.XX for my IP address)

Code:

chssrvr:Thread-32:INFO: Exception dispatching State event: Exception creating co
nnection to: XXX.XX.XX.XX; nested exception is:
       java.net.SocketException: Connection timed out:could be due to invalid a
ddress
chssrvr:Thread-32:INFO: java.rmi.ConnectIOException: Exception creating connecti
on to: XXX.XX.XX.XX; nested exception is:
       java.net.SocketException: Connection timed out:could be due to invalid a
ddress
chssrvr:Thread-32:INFO:         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(T
CPEndpoint.java:598)
chssrvr:Thread-32:INFO:         at sun.rmi.transport.tcp.TCPChannel.createConnec
tion(TCPChannel.java:203)
chssrvr:Thread-32:INFO:         at sun.rmi.transport.tcp.TCPChannel.newConnectio
n(TCPChannel.java:189)
chssrvr:Thread-32:INFO:         at sun.rmi.server.UnicastRef.invoke(UnicastRef.j
ava:117)
chssrvr:Thread-32:INFO:         at com.hie.util.process.RemoteProcessStateListen
er_Stub.processStateChanged(Unknown Source)
chssrvr:Thread-32:INFO:         at com.hie.util.process.BasicProcessMonitor.fire
StateEvent(BasicProcessMonitor.java:975)
chssrvr:Thread-32:INFO:         at com.hie.util.process.BasicProcessMonitor.fire
StateEvent(BasicProcessMonitor.java:946)
chssrvr:Thread-32:INFO:         at com.hie.util.process.BasicProcessMonitor.run(
BasicProcessMonitor.java:310)
chssrvr:Thread-32:INFO:         at java.lang.Thread.run(Thread.java:568)
chssrvr:Thread-32:INFO: Caused by: java.net.SocketException: Connection timed ou
t:could be due to invalid address
chssrvr:Thread-32:INFO:         at java.net.PlainSocketImpl.socketConnect(Native
Method)
chssrvr:Thread-32:INFO:         at java.net.PlainSocketImpl.doConnect(PlainSocke
tImpl.java:334)
chssrvr:Thread-32:INFO:         at java.net.PlainSocketImpl.connectToAddress(Pla
inSocketImpl.java:199)
chssrvr:Thread-32:INFO:         at java.net.PlainSocketImpl.connect(PlainSocketI
mpl.java:186)
chssrvr:Thread-32:INFO:         at java.net.Socket.connect(Socket.java:478)
chssrvr:Thread-32:INFO:         at java.net.Socket.connect(Socket.java:428)
chssrvr:Thread-32:INFO:         at java.net.Socket.(Socket.java:335)
chssrvr:Thread-32:INFO:         at java.net.Socket.(Socket.java:150)
chssrvr:Thread-32:INFO:         at crysec.SSL.SSLSocket.(SSLSocket.java:90
)
chssrvr:Thread-32:INFO:         at com.hie.util.ssl.HieSSLSocket.(HieSSLSo
cket.java:77)
chssrvr:Thread-32:INFO:         at com.hie.util.ssl.SSLSocketFactory.createSocke
t(SSLSocketFactory.java:327)
chssrvr:Thread-32:INFO:         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(T
CPEndpoint.java:580)
chssrvr:Thread-32:INFO:         … 8 more

Any ideas?

Topic

[Daniel Lee]

Nevermind, I figured it out.  I had window’s firewall turned on.  Evidently some functions of the GUI require the server to connect back to the client.

[Author]

Replies