[
https://issues.apache.org/jira/browse/AMQ-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597376#comment-13597376
]
Paul Gale commented on AMQ-4365:
--------------------------------
Another point worth noting is that the JDBCPersistenAdapter creates the lock
table in the database during initialization. As I had previously used this
adapter the tables were already in the database. Therefore testing my custom
lease database locker went smoothly. However anyone that uses the above
implementation as-is will get an error if the tables are not there.
Ideally the locker, not the persistence adapter, should be responsible for
managing the creation of its own lock table. I have not addressed this and
probably won't. For now I can live with a SQL script to create the schema.
> 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
> 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
