-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Rejected
-
Affects Version/s: 2.5.4.SP3
-
Fix Version/s: None
-
Component/s: callbacks
-
Labels:None
-
Environment:
JBoss EAP 5.1.2
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.