Hi Torsten & all
I spend some time trying to get the
constantPendingMessageLimitStrategy to work, but I didn't succeed.
I put the config for the topic like this:
=> the constantPendingMessageLimitStrategy is equal to the topic
prefetch number, which is what should if I got it right.
Torsten Mielke-2 wrote
>
> Once you reach an OutOfMemoryError in your JVM you should not assume that
> anything continues to work. After an OOM all side effects and errors can
> occur.
> You will need to restart the JVM.
>
I agree, and it's a work in progress. However, on the other hand, we wou
> Starting from the OutOfMemoryError, the message consumers
> don't consume any message anymore
Once you reach an OutOfMemoryError in your JVM you should not assume that
anything continues to work. After an OOM all side effects and errors can occur.
You will need to restart the JVM.
> Is there
Hi Torsten
Thanks a lot for your answer.
Even though I hadn't seen it, it doesn't really help me: indeed, it's not
the message consumers themselves who run out of memory, but the thread in
which they run. Starting from the OutOfMemoryError, the message consumers
don't consume any message anymore
An initial pointer is
http://activemq.apache.org/javalangoutofmemory.html
Not sure if you have read it already.
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Dec 9, 2011, at 9:36 AM, jp wrote:
> Hi
>
> We're using a pattern where we keep a connection/session/message consum
