Hi Tim ,
I was having a question before but now everything seems to be fine. Yes this
question is no more applicable since it got resolved and which we updated on
the other post.
Thanks,
Akhil.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Timeout-and-Failover-on-a-q
Akhil, are you asking a question, or just providing information to help
Jason (who's probably not going to see it, since his post is from 9 years
ago)? Or is your question no longer applicable since you resolved the
issue in your other post?
Tim
On Sep 20, 2016 10:26 PM, "akhil" wrote:
Hi Jaso
Hi Jason ,
I am late to the failover party and i am facing the same issue. Probably
mine is a different use case where i am intentionally putting down one of
the failover broker whether all the consumers and producers are getting
switching to the active broker remaining in the failover. I am usin
All,
I've filed an issue, and posted a patch for 5.1-SNAPSHOT, for this issue
(I've taken hbuch's patch and put it into the 5.1 source)...
See AMQ-1575
Jason
--
View this message in context:
http://www.nabble.com/Timeout-and-Failover-on-a-queue-tp13292887s2354p15328072.html
Sent from the Ac
James,
I've created a test-case here, which demonstrates clearly the main problem,
with connections created with a pooledConnection don't recover quickly, when
a broker becomes available, when the failover transport is used, with a
maxReconnectAttempts setting.
Attached is a source tar file, whi
