You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jamie Goodyear (JIRA)" <ji...@apache.org> on 2008/12/10 16:00:06 UTC

[jira] Assigned: (SMX4KNL-163) Provide default jdbc lock impl for master/slave deployments

     [ https://issues.apache.org/activemq/browse/SMX4KNL-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie Goodyear reassigned SMX4KNL-163:
--------------------------------------

    Assignee: Jamie Goodyear

> 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
>
>
> 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.