Hey Claus - can you try dumping the stack trace when the MBeans are created and removed to see the internal cause? I'm thinking along the following lines:
LOG.warn(..., new Exception())
--
View this message in context:
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-11-0-rc3-tp4690743p4690944.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
