[jira] Commented: (SMX4KNL-169) Use the start level to implement the container level locking

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SMX4KNL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48632#action_48632 ] 

Guillaume Nodet commented on SMX4KNL-169:
-----------------------------------------

To test this patch, SMX4KNL-153 patch need to be applied first.
Then, edit the {{etc//system.properties}} file and add {{servicemix.lock.level=50}} property.

This solution may work, but not when starting two processes from the same location.  You need to copy it and use the jdbc lock i suppose.  The problem is that felix won't support to use the same data/cache folder for two different instances.  A possible solution would be to change felix config to use two different folders, but it may be a bit misleading as the two instances may not have the same configuration (installed bundes, etc...).
One possible enhancement would be to have the lock file (when using the file based locking mechanism) to be specified in an alternate directory so that it could be shared by the two instances.   
The RMI / SSH port conflict has to be solved somehow too.



> Use the start level to implement the container level locking
> ------------------------------------------------------------
>
>                 Key: SMX4KNL-169
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-169
>             Project: ServiceMix Kernel
>          Issue Type: Improvement
>            Reporter: Guillaume Nodet
>             Fix For: 1.1.0
>
>         Attachments: SMX4KNL-169.patch
>
>
> This should allow hot fail-over with all bundles being already installed and ready to be started.

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