[
https://issues.apache.org/activemq/browse/SMX4KNL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48862#action_48862
]
Jamie Goodyear commented on SMX4KNL-169:
----------------------------------------
I agree that the members of each master / slave set should most definitely have
the same value for 'servicemix.lock.level'. The value for that level setting
however will need some guide lines.
* Level 1 would indicate a nearly 'cold' standby status of the core bundles.
* Level 50 would indicate a 'hot' standby status of the core bundles.
* Any level above 50 would have various behaviors based upon installed user
bundles, and as such would not be recommended.
> 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.
