> if you cycle the remote broker while the local one is down, do you get the same behavior?
I've performed the test, there's no error after clean restart of the remote broker, but the problem repeats whenever inactive destinations are purged once again. So, I suppose, your assumption is right "it is purely something in-memory on the remote broker". bad-activemq-restart.log <http://activemq.2283324.n4.nabble.com/file/t379838/bad-activemq-restart.log> -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
