are there any XA or distributed indoubt transaction in the mix? If so each would have it's own mbean after a restart, hanging off the broker mbean.
What is odd is that you still see the problem after a restart. Are the data files something you could share. I think this needs some debugging? On 13 February 2014 13:12, janhanse <espen.jul...@gmail.com> wrote: > I forgot to mention that, I did check KahaDBPersistenceAdapter in jmx, but > the Transactions attribute is empty. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/kahadb-cleanup-problem-tp4677917p4677934.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
