My primary goal in having you browse every queue with unconsumed messages was to try to force the broker to evaluate whether those messages should be expired, which would indicate that the problem was simply that the broker wasn't evaluating message expiration when no consumer was connected. If the oldest KahaDB data files suddenly disappeared after you did that, you'd know that the problem was simply that messages that should have been expired weren't being.
My goal was also to validate the unstated assumption you seem to be making that every single message sent to your broker has a JMSExpiration value set; if even one of your unconsumed messages was sent without a value for that header, it's going to keep alive your KahaDB files. Tim On Sat, Dec 19, 2015 at 5:57 AM, Shine <activ...@club.webhop.org> wrote: > Hi Tim > > i dont browse the queue .. i click on the "Queues" link in the WebConsole > to > refresh the list of queues. You see the enqueued messages and the dequeued > messages .. if the time to live of an message is over, than the counter of > the dequeued messages increase and enqueued messages decrease. > > regards > Shine > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Need-help-with-a-message-broker-configuration-tp4705074p4705210.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
