Unfortunately I don't know of any tools for inspecting KahaDB files, though
someone else here might. Sorry, I've never done much with KahaDB, so what
I know comes from the wiki page and from mailing list posts like this one.
Tim
On Tue, Sep 29, 2015 at 3:33 PM, fmansoor
Thanks Tim! Does anyone know about the txlog, and why it would be at 50gig???
We are changing the HOWL settings to see if this helps, but I'm suspecting
maybe a camel route is causing the issue. We use transacted=false in our camel
routes.. should we be setting that to true?
Regards,
Barry
Thanks Tim,
Subscribers only subscribe to queues. I restarted the server, but, that
didn't fix the problem either, haven't tried destroying all destinations
yet.
The problem occurred in production, we have to drain all the queues and
start with a new kahadb to solve the problem. I took backup of
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
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,
Yes, all the queues are empty, enqueue and dequeue counts were off for a
couple of queues, probably, because I purged them.
I am running 5.11.1, all the queues are consuming messages from virtual
topics and advisory messages are disabled.
--
View this message in context:
What about the subscribers on your topics? (Does anyone subscribe directly
to the topic, or is consumption purely from the queues on the virtual
topics?) And are any selectors in use for any client?
I'm curious whether the KahaDB files are cleaned up 1) following a broker
restart, and 2) if you
Are there any topics with unconsumed messages for offline durable
subscribers? Queues aren't the only place messages can stick around.
You might get more information by using information exposed via JMX; it
might help you find where there are still messages if indeed there are
some.
On Sep 22,
