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

[jira] Resolved: (SMX4KNL-130) Support configurable lock directory for container level locking (for master/slave deployments).

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

Guillaume Nodet resolved SMX4KNL-130.
-------------------------------------

    Fix Version/s: 1.1.0
       Resolution: Fixed

Sending        main/src/main/java/org/apache/servicemix/kernel/main/SimpleFileLock.java
Transmitting file data .
Committed revision 711745.

Thx Jamie, keep up the good work !

> Support configurable lock directory for container level locking (for master/slave deployments).
> -----------------------------------------------------------------------------------------------
>
>                 Key: SMX4KNL-130
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-130
>             Project: ServiceMix Kernel
>          Issue Type: Improvement
>         Environment: *nix and windows.
>            Reporter: Jamie Goodyear
>            Assignee: Guillaume Nodet
>             Fix For: 1.1.0
>
>         Attachments: smx4knl-130.txt, smx4knl-130b.txt
>
>
> Allow the lock directory to be configurable. Currently the lock file is located in the directory represented by the value of the "servicemix.base" property.
> {code}
> File base = new File(props.getProperty("servicemix.base"));
> {code}
> Ideally the container should support using a property that is dedicated to this locking mechanism (servicemix.lockdir?) and if it is not specified, use the servicemix.base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.