I need to get all topic datas by reading line by line over HTTP. I wrote some
java code to consume datas through http but it closes stream after reading
first line. Does apache activemq support http alive stream ? If does what
should i do ?
Code:
https://gist.github.com/kync/8483470fd5bcdcfc6446c9
Yes, memory usage should be 0 for a destination if there are no messages so
this seems like a bug. There was another memory bug fixed more recently
but that only had to do with persistent messages when using concurrent
store and dispatch. As you pointed out the best thing to do to help would
be t
It does sound like a bug, and it certainly could be the same root cause as
the bug you linked to. Does the workaround in that bug also work
(temporarily) for you?
A shot in the dark: is there any chance that you might have messages
expiring before they can be consumed? I've got a vague recollectio
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
Hi,
I have an application using ActiveMQ 5.13.5 which uses non-persistent
messages. There is a queue which has several producers and a single
consumer.
At times I see the CursorMemoryUsage not being 0 despite the queue being
empty. When this application runs for a very long time,
CursorMemoryUs
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
10 matches
Mail list logo