activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4005) Implement pluggable broker lockers
Date Thu, 30 Aug 2012 10:51:08 GMT

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

Dejan Bosanac commented on AMQ-4005:
------------------------------------

First step is donw with svn revision 1378881. New API is introduced and KahaDB/JDBC solutions
were refactored to reflect it.
                
> Implement pluggable broker lockers
> ----------------------------------
>
>                 Key: AMQ-4005
>                 URL: https://issues.apache.org/jira/browse/AMQ-4005
>             Project: ActiveMQ
>          Issue Type: New Feature
>    Affects Versions: 5.6.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.7.0
>
>
> Currently shared storage master/slave locking is a job of a persistence adapter.
> It's hardcoded in KahaDB to use shared file locking, while JDBC allows at least some
customization.
> The idea is to create general locker interface and share it across available persistence
adapters. So that for example, JDBC can use shared file lock or KahaDB use ZooKeeper lock
when it's available.
> We can also consider moving locking out of persistence layer and making it a job for
a broker.

--
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