Great, thanks for confirming that, and kudos to Gary for recognizing the
root cause.
Tim
On Feb 26, 2018 2:34 PM, "neon18" wrote:
Sorry for the delay, I finally found some time to try it out. I ran test
with
ActiveMQ 5.15.3 broker and that seems to resolve the OutOfMemoryError (OOME)
issue when
Sorry for the delay, I finally found some time to try it out. I ran test with
ActiveMQ 5.15.3 broker and that seems to resolve the OutOfMemoryError (OOME)
issue when a whole bunch of messages are put on the non-persistent queue
that exists in ActiveMQ 5.15.2 but not under ActiveMQ 5.14.5.
Regards,
Neon,
Since 5.15.3 was just released and you'd no longer need to compile from
source, would it be possible to upgrade to it to see if Gary's hunch about
the root cause of the problem was correct and the problem is fixed in
5.15.3?
Tim
On Tue, Jan 16, 2018 at 4:02 AM, Gary Tully wrote:
> Hi TIm
Hi TIm,
the regression caused references to batches of serialised messages destined
for the journal to be retained by the page cache, potentially leading to an
OOM.
The temp store used to cursor non persistent messages uses the same journal
logic and would be effected in the same way.
The trigger f
I checked with IT guys and the disk I/O is not the issue, it can handle the
data rate just fine.
I did not have time in finding a way to slow the producers.
Building from 5.15.x/3 branch from source is not an option at this time. I
also believe [AMQ-6815 KahaDB checkpoint needs to fail fast in th
On Jan 10, 2018 12:42 PM, "neon18" wrote:
We run the broker with max heap of 4G and initial of 1G (-Xmx4G -Xms1G).
We use non-persistent messages on these particular queues (3 of them in this
test).
The number of messages sent to the broker in my last "flood gate" test was
around 40,000 (40k) in
Gary,
Can you elaborate on what about this situation looks like that problem?
Because based on the information given so far, it looked to me like the OP
was simply overdriving the storage to which the temp files are written.
Tim
On Jan 12, 2018 4:04 AM, "Gary Tully" wrote:
> this looks like an
this looks like an instance of the regression from
https://issues.apache.org/jira/browse/AMQ-6815
On Wed, 10 Jan 2018 at 19:42 neon18 wrote:
> We run the broker with max heap of 4G and initial of 1G (-Xmx4G -Xms1G).
> We use non-persistent messages on these particular queues (3 of them in
> this
We run the broker with max heap of 4G and initial of 1G (-Xmx4G -Xms1G).
We use non-persistent messages on these particular queues (3 of them in this
test).
The number of messages sent to the broker in my last "flood gate" test was
around 40,000 (40k) in 5 minutes or about 8K msgs/min. After this f
Hmmm, I think I may have misinterpreted a few of the things you've written,
so I want to take a step back and recalibrate my understanding of the
behavior you're seeing.
On Tue, Jan 9, 2018 at 1:04 PM, neon18 wrote:
> > Do you get the "thread shut down" message on the first message enqueued,
> o
> Do you get the "thread shut down" message on the first message enqueued, or
> only after a certain number of messages are sent?
I believe, after a large number of of messages have been enqueued, is when
it enters the OutOfMemoryError state. In another test run, I did not see the
"Async Writer T
OK, this is a good start, thanks for working to narrow down the variables a
bit.
Do you get the "thread shut down" message on the first message enqueued, or
only after a certain number of messages are sent?
Have you set any options in your activemq.xml that might change the
broker's behavior rega
I have tried out a few things to reduce the variables, one step at a time.
1. I upgrade the ActiveMQ client libraries to 5.15.2 to match the server.
This results in same issue (OutOfMemoryError on ActiveMQ 5.15.2 server).
2. I change the memoryUsage percentOfJvmHeap from 70% to 50%, restarted the
I'm not aware of any incompatibility between a 5.12.2 client and a 5.15.2
broker, but we don't explicitly test compatibility so it's possible. But I
can't think of an obvious mechanism for an older client to cause a store
writer thread in the broker to exit, so a compatibility problem isn't where
I
We recently upgraded to ActiveMQ server 5.15.2 from 5.12.2 and when putting
some messages onto a Queue, we get the following error
ERROR | Caught an Exception adding a message: ActiveMQObjectMessage
{commandId = 2705, ...} first to FilePendingMessageCursor |
org.apache.acivemq.broker.region.cursor
15 matches
Mail list logo
