[
https://issues.apache.org/activemq/browse/SMX4KNL-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48280#action_48280
]
Guillaume Nodet commented on SMX4KNL-163:
-----------------------------------------
Good work! The configuration looks much better now :-)
For the JDBC statements to be sent to the database, wouldn't it be simpler to
just allow them to be configured through the same mechanism, as properties.
Note that the polling is only necessary when the lock has not been acquired.
When the lock has been acquired, maintaining the connection alive should be
sufficient, without committing it. If the server crashes, the connection will
be destroyed and the DB will automatically release the lock, which can then be
acquired by another instance. So the loop is necessary only when the lock can
not be acquired.
> Provide default jdbc lock impl for master/slave deployments
> -----------------------------------------------------------
>
> Key: SMX4KNL-163
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-163
> Project: ServiceMix Kernel
> Issue Type: New Feature
> Environment: All
> Reporter: Jamie Goodyear
> Assignee: Jamie Goodyear
> Fix For: 1.1.0
>
> Attachments: for-discussion-only.txt, smx4knl-163.txt
>
>
> Provide default jdbc lock impl for master/slave deployments.
> From note on SMX4KNL-106:
> By default, a file based locking mechanism is used. There is an interface
> that can be implemented to allow other locking mechanisms such as JDBC. This
> would require setting a system property for the class name of the lock (it
> can be done in etc/system.properties) and changing the shell script to add
> the needed jars to the boot classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
