[
https://issues.apache.org/activemq/browse/AMQ-1027?page=comments#action_37621 ]
Kieran Murphy commented on AMQ-1027:
My testing shows also that if a client is shutdown after failover but before it
has processed all of its prefetched
[ https://issues.apache.org/activemq/browse/AMQ-630?page=all ]
Kieran Murphy closed AMQ-630.
-
Resolution: Fixed
This is fixed, but the client using the failover protocol must be configured
with the maxReconnectAttempts argument set. If
[
https://issues.apache.org/activemq/browse/AMQ-630?page=comments#action_36761 ]
Kieran Murphy commented on AMQ-630:
---
Yes - even with the closeTimeout value set to 500ms, if I am using failover
then the client will wait FOREVER for the broker
[
https://issues.apache.org/activemq/browse/AMQ-630?page=comments#action_36154 ]
Kieran Murphy commented on AMQ-630:
---
Is it possible to get this into the 4.0 release?
After broker has shutdown, cannot shutdown a client application
[ https://issues.apache.org/activemq/browse/AMQ-630?page=all ]
Kieran Murphy reopened AMQ-630:
---
This is fixed except when I use failover. I am using failover (on client side)
to connect to a network of brokers configured with static discovery and
[ http://jira.activemq.org/jira//browse/AMQ-630?page=comments#action_35931
]
Kieran Murphy commented on AMQ-630:
---
when I turn off failover on the client side, the reconnection attempts do not
continue -- i.e. without failover, the client shuts down
[ http://jira.activemq.org/jira//browse/AMQ-630?page=all ]
Kieran Murphy reopened AMQ-630:
---
I downloaded the RC2 release, enusred that both client and broker are running
new code -- still have this problem.
What is the timeout? Do I need to
