[
https://issues.apache.org/activemq/browse/SMX4KNL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48704#action_48704
]
jgoodyear edited comment on SMX4KNL-169 at 1/14/09 7:16 AM:
-----------------------------------------------------------------
h5. Test Case:
# Install Kernel.
# Start Kernel.
# Execute: servicemix admin > create test1
# Execute: servicemix admin > create test2
# Exit from initial Kernel installation.
# Edit test1 and test2 $HOME/etc/system.properties files to include lock=true,
lock.level=50, and lock.dir=/path/to/lock
# From terminal start test1 instance.
# From terminal start test2 instance.
h6. Observations:
* JMX bind exception on second instance to be started (test2).
* Received warning on second instance to be started (test2) that the lock was
not obtained, however full console was provided (run level is 50 on both
instances).
* When first instance is stopped the second instance gains lock (test2 is now
master).
* Reconfigured test1 to start at level 0, started instance. Upon start will
wait until lock acquired to fully start SMX.
h6. Notes:
* After exiting both test1 and test2 instances I started both via the original
installation's admin console. Both are reported as "started" - each have lock
level 50 set.
* If I set one instance to have lock level 0, the other level 50, then start
both instances via the console I will see that one instance will become
started, the other will be starting. In this case the starting instance has
level 0. When i stop the currently started instance I would expect the other
instance to move from starting to started however the console does not display
this state change.
** The second instance should have been fully started and reported as such.
** When locking is in use should we report a waiting instance as "Standby"
instead of "Starting", this may be more instructive to administrators.
was (Author: jgoodyear):
h5. Test Case:
# Install Kernel.
# Start Kernel.
# Execute: servicemix admin > create test1
# Execute: servicemix admin > create test2
# Exit from initial Kernel installation.
# Edit test1 and test2 $HOME/etc/system.properties files to include lock=true,
lock.level=50, and lock.dir=/path/to/lock
# From terminal start test1 instance.
# From terminal start test2 instance.
h6. Observations:
* JMX bind exception on second instance to be started (test2).
* Received warning on second instance to be started (test2) that the lock was
not obtained, however full console was provided (run level is 50 on both
instances).
* When first instance is stopped the second instance gains lock (test2 is now
master).
* Reconfigured test1 to start at level 0, started instance. Upon start will
wait until lock acquired to fully start SMX.
h6. Notes:
*After exiting both test1 and test2 instances I started both via the original
installation's admin console. Both are reported as "started" - each have lock
level 50 set.
*If I set one instance to have lock level 0, the other level 50, then start
both instances via the console I will see that one instance will become
started, the other will be starting. In this case the starting instance has
level 0. When i stop the currently started instance I would expect the other
instance to move from starting to started however the console does not display
this state change.
** The second instance should have been fully started and reported as such.
** When locking is in use should we report a waiting instance as "Standby"
instead of "Starting", this may be more instructive to administrators.
> 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.
