activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Farhad Dehghani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4365) Allow the Lease Locker to be used with out a JDBCPersistenceAdapter - so it can be a broker lock
Date Wed, 04 Sep 2013 12:18:52 GMT

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

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

Thanks Gary. So you mean that at the moment we better not to use the Paul's lease-locker implementation
if we're using mKahaDB? 
Well right now we are in a kind of no-lock-no-luck situation, meaning that we couldn't make
the master/slave setup to work with (m)kahaDB for one of our customers, because of the filesystem
used (they're not using NFSv4 as recommended). Perhaps we need to reconsider using mKahaDB
and getting back to a single kahaDB with amq-db-lease-locker.
Is there any plan from your side to come up with a solution in the next release? 
                
> 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

Mime
View raw message