Hi, I am using an activemq 4.1.1 broker behind a load balancer, which is not JMS aware. I am using the ssl transport. The load balancer needs to check if the broker is alive, so every once in a while it opens a TCP connection to the broker's SSL port and sees if it gets a response. It doesn't send any SSL negotiation packets so the SSL handshake fails. afterwards in tries to gracefully close the socket, but the broker never closes it's side of the connection.
I noticed this leaves a lot of hanging threads - they are created in ManagedTransportConnector.createConnection (line 56). I think the root of the problem is in TransportConnector, line 147. in case there is a failure in the connection.start call the connection will be left open (correct me if I am wrong here). Was this fixed in later versions? Thanks, Hagai. -- View this message in context: http://www.nabble.com/leak-on-SSL-handshake-failure--tp16848115s2354p16848115.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
