[
https://issues.apache.org/activemq/browse/SMX4KNL-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48183#action_48183
]
Adrian Trenaman commented on SMX4KNL-163:
-----------------------------------------
Hi Jamie, how are you getting on with this?
I'm with Guillaume on the use of classname + Url, rather than using Derby:I
have in mind an architecture where ActiveMQ is deployed in SMX4 in a
master/slave scenario: I'd like the whole SMX4 kernel, including AMQ and all
bundles etc - to wait until the lock is available before start-up. Have you
thought about how your locking mechanism might interact with that of AMQ?
> 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.
