(scenario 1) If the "WireFormatInfo" is sent from the client to start negotiations and subsequently the client threads are frozen (simulated with the debugger) the broker will send back its WireFormatInfo. The brokers Inactivity monitor monitor will kick in after approx 60 seconds and tear down the connection. That is what is expected - great

(scenario 2) However If a socket.connect() is called and the connection is established but nothing has been sent across the socket and subsequently the client threads are frozen (simulated with the debugger) then the socket does seem to remain open indefinitely.

The netstat output from scenario 2 is below. 61616 is the transport connectors listening port and the 54900 is the client side port.

netstat -a | grep 61616
tcp4       0      0  localhost.61616        localhost.54900        ESTABLISHED
tcp4     244      0  localhost.54900        localhost.61616        ESTABLISHED
tcp46      0      0  *.61616                *.*                    LISTEN