[AMQ-4564] ActiveMQ creates & initializes ACTIVEMQ_LOCK in wrong database when using separate lock data source

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.5.1
• Fix Version/s: 5.9.0
• Assignee: Gary Tully
• Reporter: Tim Boemker
• Created: 31/May/13 13:25
• Updated: 03/Oct/13 21:43
• Resolved: 03/Oct/13 21:43

Description

When configured to use a secondary database for locking, ActiveMQ creates and initializes ACTIVEMQ_LOCK in the primary database. It then starts as slave because it can't lock the table in the secondary database.

Workaround: manually copy the ACTIVEMQ_LOCK table from the primary database to the secondary database.

Issue Links

• depends upon: AMQ-4365 Allow the Lease Locker to be used with out a JDBCPersistenceAdapter - so it can be a kahadb lock