History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: AMQ-1813
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Dima
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

shutdownOnMasterFailure="true" is ignored when broker starting

Created: 20/Jun/08 02:37 AM   Updated: 10/Sep/08 05:13 AM
Component/s: Broker
Affects Version/s: 5.1.0
Fix Version/s: 5.3.0

Time Tracking:
Not Specified


 Description  « Hide
If slave broker cannot connect to master when slave broker starting, slave broker doesn't stop starting and starts all connectors
I think it's a bad behavior. It must shutdown when shutdownOnMasterFailure="true"

 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
ying - 15/Jul/08 08:19 AM
using tcp://master:61616 for masterConnectorURI and shutdownOnMasterFailure="true" , I got the same result. I think this needs to be fixed too.

but using failover://(tcp://master:61616)?maxReconnectAttempts=3 as the masterConnectorURI , after 3 failed attemp, it will shut down the slave. so shutdownOnMasterFailure is not ignored in the failover protocol case.


Dima - 15/Jul/08 08:47 AM
2ying

Your logic behaviour is result of race condition. Broker is already started when limit of maxReconnectAttempts=3 is exceeded