Here's a sample URI. failover:(tcp://QGMQDEV1:10200?transport.UseInactivityMonitor=false&transport.UseLogging=true,tcp://QGMQBETA1:10200?transport.UseInactivityMonitor=false&transport.UseLogging=true)?transport.AsyncConnect=true&transport.AsyncTimeout=20000
I had this just happen to me again. I'm testing a fix against trunk right now so I will keep an eye on this while using trunk. As far as replicating it with a small example I'm not exactly sure how to do it, as generally the services shut down fine. -- View this message in context: http://activemq.2283324.n4.nabble.com/NMS-ActiveMQ-provider-infinite-loop-on-disposal-tp3056196p3064310.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
