We are frequently getting 'java.net.SocketException' in ActiveMQ logs. Aftr that the number of consumer becomes 0 and message becomes pending. java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///10.51.19.88:2855
Our Client is configured such that when it gets any asynchronous Exception from JMS Server, it reconnects after 20 minutes. So after 20 minutes again number of consumer becomes 1 and the messages pending in the ActiveMQ queue get transported to Client. We are not sure what is causing connection to get reset. Is it Firewall? If yes is it Firewall from broker side or from client side? Or any router in between is causing the connection to be dropped? We will appreciate any valuable input. -- View this message in context: http://activemq.2283324.n4.nabble.com/Getting-java-net-SocketException-in-ActiveMQ-logs-frequently-tp4666138.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
