[
https://issues.apache.org/activemq/browse/SMX4KNL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48656#action_48656
]
Guillaume Nodet commented on SMX4KNL-169:
-----------------------------------------
Another possible idea would be to implement the locking at the jbi level, where
all SAs would be in a stopped state until the master crashes, which would make
the salve start the SAs. However, i think the same problem as the start level
lock mechanism would occur: you can't really start two instances from the same
folder, and you have to configure different ports. Anyway, locking at the jbi
level may provide a faster way to come the slave to a fully operational state,
though i'm not sure it's worth it compared to start level lock mechanism.
I guess we need to experiment a bit and see what the delay is for a typical
servicemix 4 installation (with one SA). My guess is that it should be
sufficient.
> 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.
