When socket connections are terminated "hard". E.g. when the remote client dies, we get the following exceptions on the server:
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
11:57:18,112 ERROR [ServerThread] failed
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at java.io.DataInputStream.readByte(DataInputStream.java:331)
at org.jboss.serial.io.JBossObjectInputStream.readByte(JBossObjectInputStream.java:127)
at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:441)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:323)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:385)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239)
This is all pretty harmless, but quite ugly.
Any chance of having the exception handled on the server side and a nice message like "connection has died - cleaning up state" instead?
