have you looked at startupMaxReconnectAttempts and maxReconnectAttempts.
On Tue, Apr 29, 2014 at 7:23 AM, Gary Tully <gary.tu...@gmail.com> wrote: > there is currently no way to say retryCurrent X times before trying an > alternative url in the list and url must be unique so > there is no way to hack in duplicates. > maybe create a jira to track the enhancement to allow a retryCount on > the current url before moving on through the list. > > On 24 April 2014 09:24, Charels_Li <iamle...@gmail.com> wrote: > > Hi guys. I am using failover + broker network for disaster transfer. So i > > config two brokers using static network and on client side i specifies > > failover like this. > > > > failover:(tcp://localhost:61617,tcp://localhost:61618)?randomize=false) > > > > My question is, when i kill the main broker, I may need the client take a > > few seconds to see if it could regain connection to the main broker > before > > any connect attempt to the backup one. > > > > Any idea is welcome. > > > > > > > > -- > > View this message in context: > http://activemq.2283324.n4.nabble.com/delay-failover-transfer-tp4680504.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > -- > http://redhat.com > http://blog.garytully.com >
