Previously, when a slave broker in a master-slave pair failed back to the original master broker, the JMX sever on the slave broker did not restart and could no longer be used. As a result of this issue, you could not manage or control the slave broker via JMX. However, other management methods (for example, via Jolokia or HTTP) were unaffected. This issue is now resolved. When a slave broker fails back to the original master broker, the JMX server is restarted.

https://github.com/sjhiggs/activemq-artemis/tree/ENTMQBR-2932/examples/features/ha/replicated-failback mvn clean verify Observe result during test: querying JMX server: service:jmx:rmi: ///jndi/rmi://localhost:1199/jmxrmi jmx attempt failed: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused (Connection refused)] TEST 3: server0Live: true :: server1Live: null