I wasn't aware of any reason that the logging config and debugging techniques described on that page would not work properly with mKahaDB. Can you please elaborate on the failure you referenced?
Also, Sunil rightly pointed out that the behavior you've described can be caused by uncommitted transactions. Are transactions in use anywhere, and if so have you explored the possibility that they might not be getting committed? What version of ActiveMQ are you using? Tim On Fri, Apr 19, 2019, 5:18 AM TC <thiam.che...@gmail.com> wrote: > Based on the link > > https://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html > I tried to setup the journal log to see which the reasons for the missing > logs. But failed -my setup is using mKahadb rather than Kahadb. > > I only knows which queue that has lots of journal logs - in my case - it is > a queue that get forwarded from a topic - sample of the activemq.xml > > <compositeTopic name="MyEventTopic"> > <forwardTo> > <queue physicalName="MyEventQueue1" /> > <queue physicalName="MyEventQueue2" /> > </forwardTo> > </compositeTopic> > > The queue that fills up journal logs in mKahadb are MyEventQueue1 and > MyEventQueue2. > And in my activemq.log there are many many many duplicate message detected > for MyEventQueue1 and MyEventQueue2. > > And these journal logs get deleted everytime I restart ActiveMQ broker. > > > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
