[
https://issues.apache.org/jira/browse/AMQ-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752512#comment-13752512
]
Paul Gale commented on AMQ-4365:
--------------------------------
Since making this initial request back in March I have completed the locker
implementation. Therefore my earlier comment about needing a SQL script is no
longer relevant. The locker auto-creates the table if it's missing in the same
manner as the JDBCPersistenceAdapter.
Note that my implementation is a total hack, e.g., no tests. It was designed to
see me through until I can upgrade to ActiveMQ 5.9.0 at which point I plan to
switch storage strategy to Replicated LevelDB.
If there's any interest in seeing my implementation, let me know and I'll put
it up on Github.
> 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_su7vm...@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
