[AMQ-4365] Allow the Lease Locker to be used with out a JDBCPersistenceAdapter - so it can be a kahadb lock

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.8.0
• Fix Version/s: 5.9.0
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 08/Mar/13 12:27
• Updated: 15/Jan/14 22:24
• Resolved: 20/Sep/13 14:36

Description

The locker interface needs another configure option to provide a broker service, or needs to be brokerService aware so that a locker can get identity and access to the io exception handlers.

The lease database locker is dependent on the jdbc pa to get statements and data source. It should be possible to configure these independently such that it can be used standalone as a broker lock. So setters for each.
This will help sort out some of the dependencies between broker and lock implementations. also making it possible to use a lease lock with kahadb for example.
some context: http://mail-archives.apache.org/mod_mbox/activemq-users/201303.mbox/[e-mail]%3E

Issue Links

• is depended upon by: AMQ-4564 ActiveMQ creates & initializes ACTIVEMQ_LOCK in wrong database when using separate lock data source