We are using ActiveMQ version 5.9.0 and using the Failover Transport with a
single host and suspect that a JMS connection failure
(transportInterrupted)/re-connection (transportResumed) is sometimes causing
a thread which is dispatching a message to the Broker to become stuck/hung.
Once this occur
I am sending a message to a unique single consumer and after some timeout
period expires my application attempts to reclaim the message via a message
selector utilizing a unique message property. This generally works very
well. However, I noticed unwanted behavior when the Consumers network
conne