"vons1234" wrote : Hi,
| Every now and then i am seeing following exception in my server.log
| java.net.SocketException: Socket closed
| | at java.net.SocketInputStream.read(SocketInputStream.java:162)
| | ...
| | at java.io.ObjectInputStream.readByte(ObjectInputStream.java:875)
| | at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:31
This happens when the network connection is terminated (either by hardware problems,
firewall, router, os buffer shortage, jmx-stop of server or restart of the other side).
I dont think your (client) code can or is causing this.
However your client code is missing proper error and resource handling. Especially you
should use finally blocks to close the connection. This can explain leaking connections,
which lead to leaking threads and this quickly (on hpux) leads to out of native memory.
View the original post :
Reply to the post :