Tim Bain wrote > Can you please explain what aspects of your answer are expected to solve > the specific problem that Martin is describing in this thread, and why > they're expected to solve it? At first glance, I don't see why using > synchronous TCP closes would influence failover of connections managed by > a > connection pool, so I'd like to better understand what you're suggesting. > > Tim > > On Jul 21, 2016 3:01 AM, "crishel.yumul" <
> crishel.yumul@ > > wrote: > >> Hi, >> configure your broker URL with this >> failover:tcp:// > <master> > : > <port> > ,tcp:// > <slave> > : > <port> > ?closeAsync=false >> >> Hope it helps! >> >> Regards, >> Crishel Yumul >> DevOps >> TORO Limited >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Consumer-does-not-reconnect-tp4714039p4714219.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> "Failover" to specify you're using master/slave setup "TCP" usage is for the clients connecting to a remote broker. You can use different transport reference depends on your broker setup, hence, http://activemq.apache.org/uri-protocols.html Since I'm using TCP protocol ref, closeAsync is one of the many config options for TCP, remember every protocol defines its own config option. closeAsync by default is true, set it false so that alive brokers can send signal before socket connection closed. -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-does-not-reconnect-tp4714039p4714281.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
