On 15.03.2017 13:01, Hidekazu wrote:
Dear cschneider

Thanks for teaching me a good way to avoid increasing kahaDB.
I came to know that dead letter queues are one of keys.

By the way, I have two questions. (I'm sorry, I'm ActiveMQ newcomer...)

1. How do I see dead letter queues?
    I want to make sure whether dead letter queue make kahadb bigger.
    command? filename for dead letter queue?
You can see dead letter queues like any other queues in the web console.
There is no specific filename as in the default kahadb setup all queues are handled in the same set of kahadb journal files.


2.I was able to keep KahaDB small by deleteing pending queues and
    delete journal files.
    however, I noticed that db.data kept increasing.
    I think this is a different problem from managing kahaDB journals.
    Do you know how you keep db.data small?
Be careful about deleting journal files. This can easily damage the integrity and you can loose messages. A journal file is automatically deleted when activemq finds that all entries in there are fully handled.
So simply manage your queues and activemq takes care of the journals.

If activemq does not seem to delete old journal files then one thing you can do is write a small script that reads the messages of long term queues like dead letter queues and just writes them to another queue. This way the old message is done for activemq and the new message will be in the newest journal.

db.data is just a kind of cache of the meta data from the journals. So when activemq is stopped you can safely delete it.
See e.g. https://access.redhat.com/solutions/276323

Christian


Thanks
Kawai



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/The-size-of-KahaDB-doesn-t-seem-to-decrease-tp4723669p4723778.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Reply via email to