Thanks Tim for your reply. Yes, the issue seems to be TCP connections seem to be in bad state - we are not sure what is causing this behavior but guessing it could be related to firewall idle session timeout (or possibly some other firewall rule?) which is dropping the TCP connection on the client machine but not the server machine. We believe it cannot be kill -9 as the client process is still running and continues to establish new TCP connections to the server
We don't have complete control or access to the firewall as we don't own them. Can you please elaborate on parameters for ActiveMQ keep-alive features to detect the broken TCP connections? Thanks for your feedback! -- View this message in context: http://activemq.2283324.n4.nabble.com/TCP-connections-leak-tp4697435p4697508.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
