Why does CLM 6.0 hang when running https://hostname/jts/setup behind a proxy server?
Hi,
I have installed CLM + JTS 6.0 on WAS 8557 and am trying to go to the /jts/setup url.
In my network, I am behind a proxy server - the server where I am running CLM + JTS can't hit the internet.
When I go to https://<hostname>:9443/jts/setup , the page just hangs. I can see the WebSphere java process is trying to hit an IP outside my network and feel like this is probably the cause of the hang.
This is the output from netstat -pant | grep <pid number of websphere>
root@rtctesting logs # netstat -pant | grep 5805
tcp6 0 0 :::9060 :::* LISTEN 5805/java
tcp6 0 0 :::9100 :::* LISTEN 5805/java
tcp6 0 0 :::8880 :::* LISTEN 5805/java
tcp6 0 0 :::9043 :::* LISTEN 5805/java
tcp6 0 0 127.0.0.1:1527 :::* LISTEN 5805/java
tcp6 0 0 :::9080 :::* LISTEN 5805/java
tcp6 0 0 :::2809 :::* LISTEN 5805/java
tcp6 0 0 :::9402 :::* LISTEN 5805/java
tcp6 0 0 :::9403 :::* LISTEN 5805/java
tcp6 0 0 127.0.0.1:9633 :::* LISTEN 5805/java
tcp6 0 0 :::9443 :::* LISTEN 5805/java
tcp6 38 0 9.190.39.35:59318 9.190.39.35:9443 CLOSE_WAIT 5805/java
tcp6 0 0 9.190.39.35:9443 9.190.39.35:59324 ESTABLISHED 5805/java
tcp6 0 0 9.190.39.35:9443 9.190.39.175:56285 ESTABLISHED 5805/java
tcp6 0 0 9.190.39.35:59324 9.190.39.35:9443 ESTABLISHED 5805/java
tcp6 38 0 9.190.39.35:59317 9.190.39.35:9443 CLOSE_WAIT 5805/java
tcp6 0 1 9.190.39.35:59276 118.215.115.219:80 SYN_SENT 5805/java
118.215.115.219 resolves to a118-215.115-219.deploy.akamaitechnologies.com - so not really any hints there about what JTS is trying to get at.
There's eventually (after about 5 minutes) an entry in the SystemErr.log. Despite the error, my request in the browser just keeps hanging (white screen and everything) .
[9/18/15 17:36:20:721 AEST] 00000088 SystemErr R java.net.ConnectException: Connection timed out
[9/18/15 17:36:20:721 AEST] 00000088 SystemErr R at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:412)
[9/18/15 17:36:20:721 AEST] 00000088 SystemErr R at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:271)
[9/18/15 17:36:20:722 AEST] 00000088 SystemErr R at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:258)
[9/18/15 17:36:20:722 AEST] 00000088 SystemErr R at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:376)
[9/18/15 17:36:20:722 AEST] 00000088 SystemErr R at java.net.Socket.connect(Socket.java:546)
[9/18/15 17:36:20:722 AEST] 00000088 SystemErr R at java.net.Socket.connect(Socket.java:495)
[9/18/15 17:36:20:722 AEST] 00000088 SystemErr R at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
When I've seen this sort of thing before, I add the -DhttpProxyHost and -DhttpProxyPort JVM arguments and it usually gets past it, but it isn't working this time - perhaps whatever JTS is trying to do isn't proxyable?
Any ideas about workarounds? Thanks very much!
Graham.
Comments
Donald Nong
Sep 27 '15, 10:07 p.m.I haven't see such problem before. If you install CLMHELP on the server, it does try to contact ibm.com to grab the help content on the internet, but I haven't see any cases where such contact can hang the server. If you try to access other applications (such as snoop) on the WAS server, will the same problem appear?