Ok... I figured out what was going on. I will file a ticket on this shortly.
When the master broker is undergoing a controlled shutdown, the
BrokerService.stop() method stops in this order:
* services
* connectors
* registered vm transports
* broker
So there is a period where the broker will
We are using the ActiveMQ in an embedded mode in our application. It may be
difficult to reproduce in a test case because of the intermittent nature...
On inspection of the code below (from MasterBroker.java), it seems that an
exception syncing to the slave is logged but otherwise ignored. Doesn
Any chance you can create a test case to reproduce this?
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
Connect
Sorry, the master exception log message includes a modification we made to
the logging on slave failure to distinguish failure conditions (see
AMQ-2459).
Normally it would say "Slave Failed" with the exception. Full exception
trace returned from slave:
java.net.SocketException: socket closed
