[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-4365) Allow the Lease Locker to be used with out a JDBCPersistenceAdapter -
From:       "Paul Gale (JIRA)" <jira () apache ! org>
Date:       2013-08-30 18:32:52
Message-ID: JIRA.12636015.1362745651906.61765.1377887572384 () arcas
[Download RAW message or body]


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

Paul Gale commented on AMQ-4365:
--------------------------------

See here: https://github.com/ppaul/amq-db-lease-locker

I warn you, it's a hack but it does work.
                
> 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


[prev in list] [next in list] [prev in thread] [next in thread]