| Key: |
MB-590
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Dejan Bosanac
|
| Reporter: |
Stan Lewis
|
| Votes: |
0
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
When you set up a shared filesystem master and slave(s) you can manage the master instance via JMX or activemq-admin, however all of the slaves block on acquiring the database lock before starting up the JMX management context, which means you cannot attach jconsole to a slave or run any activemq-admin commands against it.
|
|
Description
|
When you set up a shared filesystem master and slave(s) you can manage the master instance via JMX or activemq-admin, however all of the slaves block on acquiring the database lock before starting up the JMX management context, which means you cannot attach jconsole to a slave or run any activemq-admin commands against it. |
Show » |
|
There's no way to monitor a slave broker in a shared filesystem master/slave setup via JMX
The slave broker can now be stopped with
bin/activemq-admin stop --jmxurl service:jmx:rmi:///jndi/rmi://localhost:55564/jmxrmiPlease also consult the comment in the original https://issues.apache.org/activemq/browse/AMQ-2306
issue