r
> trigger) producers to reconnect to the "secondary" (or backup) broker
> before
> the "primary" broker shuts down? If there is no producing on the "to be
> shut
> down broker" and remaining messages are consumed before the shutdown then
> the failover w
nsumed before the shutdown then
the failover would not cause messages to be lost.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-backup-true-does-not-work-with-failover-transport-tp4728967p4729101.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
tially have backup connections to
>> amq01 (only to amq02) reconnected to amq02. The original number of
>> connections were 160-160 to amq02 which was no more the case.
>>
>>
>> I repeated the test and I restarted everything not only once but the
>> behaviour didn&#x
connected to amq02. The original number of
connections were 160-160 to amq02 which was no more the case.
I repeated the test and I restarted everything not only once but the
behaviour didn't change.
I would appreciate your feedback.
--
View this message in context:
http://activemq.2283324
er of
connections were 160-160 to amq02 which was no more the case.
I repeated the test and I restarted everything not only once but the
behaviour didn't change.
I would appreciate your feedback.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-backu
e.com/ActiveMQ-CPP-backup-true-does-not-work-with-failover-transport-tp4728967.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I'd recommend using the latest release which has some backup handling
fixes (3.9.4)
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
tempted to reconnect to the first broker 4 times but never to the second
broker, which was up.
Any ideas how I could get "backup=true" to work? May it be a bug in the
library?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-backup-true-does-no
