That can happen if you have topics whose consumers don't consume all the messages, either due to selectors or due to consumers being offline when messages are published. (Do you have topics? And are advisory messages enabled?) If neither of those are the case, there are probably unconsumed messages somewhere.
By "nothings seems out of ordinary", did you mean that for each destination, the enqueue and dequeue counts are equal? I can't answer any questions about checkForCorruptJournalFiles, but maybe someone else here can. Also, you've never said what version you're running. Tim On Sep 23, 2015 12:21 AM, "fmansoor" <faisal.mans...@gmail.com> wrote: > Thanks Tim, there are no durable subscribers, this server does not have any > networked brokers either. > > Went though JMX information, but, nothings seems out of ordinary. Except > that the total dequeue count (118) is less than total enqueue count (242). > > I know about heckForCorruptJournalFiles, but, is there an way to check for > corrupt journal entries without restarting the server? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/KahaDb-journal-file-are-not-getting-recycled-and-Total-Message-Count-is-negative-tp4702208p4702212.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
