[AMQ-5208] ActiveMQ restart when Locker looses lock weakness

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.9.1
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Philippe Cuvecle
• Created: 04/Jun/14 13:08
• Updated: 13/Mar/22 14:08
• Resolved: 13/Mar/22 14:08

Description

The feature implemented in AMQ-4526 does not help if the restart does not succeed

Imagine the following scenario : 2 AMQ configured with jdbcPersistenceAdapter

• At the beginning AMQ1 is master, AMQ2 is slave
• database targeted by jdbcPersistenceAdapter shutsdown or connectivity is lost
• AMQ1 restarts but because DB is not back during restart it dies
• AMQ2 tries to get the lock every 10s and stay alive
• DB is back, AMQ2 becomes master
• DB shutdown again, AMQ2 restart and dies for the same reason AMQ1 died
  -> We don't have any AMQ up

When a lock is down why don't you just deny AMQ connections and retry to become master on a regular basis ?
More generally how can we have a master/slave high availability configuration that can tolerate long storage unavailability ?

Issue Links

• relates to: AMQ-4526 ActiveMQ should automatically restart if a Locker looses it's lock.