[jira] [Commented] (AMQ-4365) Allow the Lease Locker to be used with out a JDBCPersistenceAdapter - so it can be a broker lock

["Farhad Dehghani (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757649#comment-13757649 ] 

Farhad Dehghani commented on AMQ-4365:
--------------------------------------

My understanding is that when using multiple kahaDB (mKahaDB) persistence adpaters, we only need one lease-database-locker for all the adapters, right? The xsd requires that we define one for each kahaDB. Does it mean we end up with multiple locker-threads checking and/or updating the lock-table? 
How does it work with mKahaDB really?

                
> Allow the Lease Locker to be used with out a JDBCPersistenceAdapter - so it can be a broker lock
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4365
>                 URL: https://issues.apache.org/jira/browse/AMQ-4365
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.8.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.9.0
>
>
> 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/%3CCAJ5znhurUZ+aEWsaaBAjtwBbpKWn06RyyyT6NqsDg_Su7vMOcg@mail.gmail.com%3E

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira