[ https://issues.jboss.org/browse/JBREM-1317?page=com.atlassian.jira.plugin... ] Doug Grove updated JBREM-1317: ------------------------------ Description: When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. The code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. This results in the code waiting for the full duration of the configured timeout. was: When a client dies or is killed, the failure is actually detected in org.jboss.remoting.transport.socket.MicroSocketClientInvoker: (NEW ClientSocketWrapper[Socket[addr=/10.0.0.212,port=36600,localport=4458].d3e837]) got Exception: java.io.IOException: Broken pipe The "Broken pipe" exception means that the client has disconnected and can not return. This exception is treated in the code a retry-able, however. This is ignored, however, and the code carries on, finally calling BisocketClientInvoker.createSocket(). This code then waits for a socket to appear in a list. I can see no way for a new socket to ever appear in the list. This results in the code waiting for the full duration of the configured timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira