Affects Version/s: 5.3.0
Fix Version/s: None
Linux 2.6.31-22-generic-pae #60-Ubuntu SMP Thu May 27 01:40:15 UTC 2010 i686 GNU/Linux
In an environment where multiple ActiveMQ broker servers are running on the same host, the "activemq-admin stop" command will shutdown other instances if the requested instance is already down.
This is very dangerous behavior in the case where a user inadvertently attempts to shutdown a broker instance which is already down - instead of getting an error message, or the command being a no-op, a different instance than requested will be shutdown instead.
- Install ActiveMQ into SOMEDIR/broker_a and configure port and name.
- Install ActiveMQ into SOMEDIR/broker_b and configure unique port and name.
- Start broker_a - broker_a/bin/activemq (or alternatively activemq-admin start)
- Start broker_b - broker_b/bin/activemq (or alternatively activemq-admin start)
- Stop broker_a - broker_a/bin/activemq-admin stop
- Try to stop broker_a again - broker_a/bin/activemq-admin stop – THIS WILL RESULT IN broker_b SHUTTING DOWN
If there are three or more instances, the result is the same - "activemq-admin stop" will shutdown instances other than the one requested.