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 Wed, 05 Sep 2012 12:55:07 GMT

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

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

This failure was not introduced by the change. It's a long-known issue. Gary created https://issues.apache.org/jira/browse/AMQ-4020
and https://issues.apache.org/jira/browse/AMQ-4021 to deal with 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