topic JBoss - Java error? in Application Networking

JBoss - Java error?

jcotter — Thu, 16 Jun 2005 17:07:29 GMT

We managed to get the CSS units up and running and I am just using TCP as my application keepalive type. However, our servers that are behind the CSS boxes are getting this error message every few seconds. Anyone with any insight? Should I change teh keepalive type to something that suits Java a little better???

09:48:09,147 ERROR [PoolTcpEndpoint] Socket error caused by remote host /10.99.72.100

java.net.SocketException: Invalid argument

at java.net.PlainSocketImpl.socketSetOption(Native Method)

at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:264)

at java.net.Socket.setTcpNoDelay(Socket.java:826)

at org.apache.tomcat.util.net.PoolTcpEndpoint.setSocketOptions(PoolTcpEndpoint.java:503)

at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:515)

at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)

at java.lang.Thread.run(Thread.java:595)

Re: JBoss - Java error?

jfoerster — Mon, 20 Jun 2005 15:47:23 GMT

HI,

seems as if your server has sort of a problem establishing a connection with the CSS. This is might be because the CSS only openes the port and immediatelly closes it again.

java.net.SocketException: Invalid argument

(connecting to a different host) The server is not running (nobody is listening on the specified port).

(connecting to a different host) The host is not reachable. (see http://www.innovation.ch/java/HTTPClient/errors.html)

I found some other postings in the Web stating such errors with apache...

Have you tried to setup a direct telnet connection to the port from your PC? What's the result of this?

If the server is running a http port have you tried the keepalive head?

Kind Regards,

Joerg

Re: JBoss - Java error?

jcotter — Mon, 20 Jun 2005 18:16:47 GMT

After doing some packet sniffing we discovered that the problem was that the CSS devices were doing what they were supposed to be doing with their TCP keepalives. The server hated that there was just a TCP connection opened every few seconds and no business transacted. I changed the keepalive type to http and wham-o, no more problems. Thanks for the response, however.