Dear Tim
Thanks for your always help to understand ActiveMQ.
I didn't know ActiveMQ first at all but thanks to you ,
now I became to be confident about it a little.
> But let's step back for a second: why are you trying to limit the size of
> db.data in the first place? Why is its current size a
No, indexCacheSize is not a limit on the size of the index. It specifies
how much of the index should be stored in memory (which is fast); if that's
not enough to hold the full index, the remaining content will be paged in
from db.data on disk (which is slow).
As I understand it, db.data grows onl
Yes, the DLQ is a queue, irrespective of what destination type the messages
were originally sent to.
Tim
On Mar 17, 2017 1:49 AM, "Hidekazu" wrote:
Dear Tim
Thanks for helping me understand the specification of ActiveMQ.
Thanks to you, I understand ActiveMQ more than before.
I could delete d
Dear Tim
Thanks for helping me understand the specification of ActiveMQ.
Thanks to you, I understand ActiveMQ more than before.
I could delete data.db safely.
(Thank you very much!!)
By the way, I use ActiveMQ with TOPIC (not queue.)
Will I see DLQ in queue tab in ActiveMQ　console when my Active
Dear cschneider
Thanks to your advice, we could delete data.db safely.
I found that activemq.xml had a parameter which limits the cache size.
Is the parameter below perhaps for db.data?
Or is it different from the limit for db.data because it explains that
"cached in memory."
http:/
1a) The default name for the dead letter queue is DLQ. You can use the web
console (http://activemq.apache.org/web-console.html) to view the queues
the broker has. Note that ActiveMQ will automatically create a destination
when the first message is published into it, so if it doesn't exist then it
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 m
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
We recently had a case at a customer where some dead letter queues
retained messages for a long time while messages in all other queues
were short lived. The long lived messages were messages from short lived
queues that were moved to the dead letter queues. This created very
sparsely populated
Dear Tabish121
As you introduced the helpful and fundamental specification of kahaDB to me,
the reason of the size of kahaDB kept increasing was really elementary.
(I'm sorry)
there were a lot of pending queues in ActiveMQ and that was the reason.
anyway, your advice was really helpful.
thanks a
Thanks Andreas
The article you introduced me was very helpful to understand the
specification of kahaDB.
I have to say there was a miss-communication among our developer team.
I heard that there was no pending queue in ActiveMQ, however,
There were a lot of pending queue in ActiveMQ and that was
Best place to start is in the docs, see why the files are being retained.
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html
On 03/13/2017 06:39 AM, Hidekazu wrote:
I use ActiveMQ ver 5.14.3.
I thought the size of kahaDB wouldn't get bigger if ActiveMQ could sent dat
Hi there,
we had the same issue when we were using topics and had durable subscribers
which wouldn't connect for up to 4 days.
The kahadb files would only be cleaned up when the last durable
subscriber has
received the message. In our case the topic in in question didn't have a
lot of traffic
I use ActiveMQ ver 5.14.3.
I thought the size of kahaDB wouldn't get bigger if ActiveMQ could sent data
to subscriber.
However, the size of kahaDB continues increasing even it can send all the
data to subscriber.
There is no pending queue in GUI management console.
Is there any necessary paramet
14 matches
Mail list logo
