[
https://issues.apache.org/activemq/browse/SMX4KNL-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48187#action_48187
]
Jamie Goodyear commented on SMX4KNL-163:
----------------------------------------
Hi Adrian,
If we use the classname + Url approach, rather than an internal Derby instance,
then we should be able to point SMX4 kernel lock at the AMQ database. Reusing
the AMQ DB lock table or a second locking table just for SMX4 could be made
into a configuration preference.
The first scenario would make SMX4 wait upon gaining the AMQ lock, the later
would allow SMX4 kernel to gain a lock independently of the AMQ instance. This
design & deployment scenario will need some testing on separate hosts to see if
its feasible.
> 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: 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.
