I get the same error even with closing the context properly.
But application still working. It is kind of annoying to have it in logs so please a statement to get rid off would be of great help.
This has been resolved (http://jira.jboss.com/jira/browse/JBREM-156). Problem is that was logging exceptions when the client would disconnect, causing the socket reset. This is normal behavior, but was not catching that exception specifically and logging it as such.
If just can't bear to see it any more in the logs, can add the following to the log4j.xml file in the conf directory.
<category name="org.jboss.remoting.transport.socket.ServerThread"> <priority value="FATAL"/> </category>
so is there a patch for the JBREM-156 fix (Better exception handling within socket server invoker) available to download ??
i have exactly the same problem.. any ideas about the patch?