Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 4 Sep 2013 19:51:01 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12636015.1362745651906.80262.1378324261947@arcas>
In-Reply-To: <JIRA.12636015.1362745651906@arcas>
References: <JIRA.12636015.1362745651906@arcas>
Subject: [jira] [Commented] (AMQ-4365) Allow the Lease Locker to be used
 with out a JDBCPersistenceAdapter - so it can be a broker lock
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Tully commented on AMQ-4365:
---------------------------------

@Farhad thinking more, you should be able to make it work for mkahadb, just have a single kahadb nested instance use a locker and for all others useLock="false". Maybe even configure a static destination and kahadb for that destination that will be responsible for locking. In that way there will be something concrete for the slave to lock on also so there always be contention at startup.

We will try to get to a fix - both brokerService and MultiKahaDB supporting LockableServiceSupport for 5.9
                
> 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