Here's my setup: ActiveMQ 5.1 NMS 1.0 with connection URL: tcp://machinename:61616?jms.prefetchPolicy.all=1
I'm having a problem with AMQ/NMS when the network connection is lost. To simulate this problem I manually disable/enable the network interface on my local box during the course of the test. When the network connection is lost, the client enters a loop until the connection is re-established. However, even after the client creates a new connection, session, consumer, and registers a listener no messages are received. In order to receive message I had to restart the broker. I used the JMX console and notice that the old connection is still listed, which is reasonable because the client is not able to shut down cleanly when the network unexpectedly goes down. I also observed that if I manually close the old connection (using the JMX console) the client does begin to receive messages. What can I do to fix this situation? It's not practical to manually restart the broker or manually manage connections when we have network blips. -- View this message in context: http://www.nabble.com/NMS-and-network-connectivity-tp19882147p19882147.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
