plication (ActiveMQ or anything else) is running out of memory
> > because I tried to cut the memory limits too close just to save a
> > little RAM.
> >
> > All of that is how to work around the fact that before you try to
> > browse your queue, something else has al
oblem.
>
> If you want to go down that path, one thread to pull on is your
> observation that you "can browse/consume some Queues _until_ the
> #checkpoint call after 30 seconds." I assume from your reference
> to checkpointing that you're using KahaDB as your
istence store. Can you post the KahaDB
portion of your config?
Your statements here and in your StackOverflow post (
http://stackoverflow.com/questions/34679854/how-to-avoid-blocking-of-queue-browsing-after-activemq-checkpoint-call)
indicate that you think that the problem is that memory isn't
If I increase the JVM max heap size (4GB), the behavior does not change.
In my point of view, the configured memoryLimit (500 MB) works as
expected (heapdump shows same max. size for the TextMessage content,
i.e. 55002 byte[] instances containing 539 MB total).
However, trying to browse a queue sh
If you increase your JVM size (4GB, 8GB, etc., the biggest your OS and
hardware will support), does the behavior change? Does it truly take all
available memory, or just all the memory that you've made available to it
(which isn't tiny but really isn't all that big)?
Also, how do you know that th
(related issue: https://issues.apache.org/jira/browse/AMQ-6115)
There's a problem when Using ActiveMQ with a large number of Persistence
Queues (250) á 1000 persistent TextMessages á 10 KB.
Our scenario requires these messages to remain in the storage over a
long time (days), until they are consu
