Hi,
What ActiveMQ did you test ?
Regards
JB
> Le 2 juin 2020 à 17:26, sainath a écrit :
>
> We tried just JMX which made a big difference but it seems that advisories
> still had some effect and decided to be safe and disabled both. If someone
> is able to read heap dumps we would be more
We tried just JMX which made a big difference but it seems that advisories
still had some effect and decided to be safe and disabled both. If someone
is able to read heap dumps we would be more than happy to collect them to
verify what if any objects are being retained.
--
Sent from:
Does disabling one but not both of those things also fix the problem? Or is
the problem only eliminated if both are disabled?
Tim
On Mon, Jun 1, 2020, 7:44 AM sainath
wrote:
> Hi All,
>
> We disabled JMX and advisories, this seems to fix the memory issue.
>
> In the ActiveMQ.xml file we
>
>
Hi All,
We disabled JMX and advisories, this seems to fix the memory issue.
In the ActiveMQ.xml file we
Added these flags useJmx="false" and advisorySupport="false"
eg:
http://activemq.apache.org/schema/core;
brokerName="localhost" dataDirectory="${activemq.data}" useJmx="false"
We have tried with java Update 181 and it still ran out of memory. Could you
please help us to provide some suggestion on this.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Are you by any chance using CMS as your GC strategy? It's got a nasty
shortcoming where because it doesn't compact Old Gen, it's possible to have
heap fragmentation that means it's not possible to allocate contiguous
space for a large object even though there's still space free. If so, you
should
Hi All,
Yes, we have configured the limits on memory usage in the broker settings.
We also checked the heap dump and found that still 500 MB free space
available. So what could you be the reason for OutOfMemoryError in activeMQ
Also we are monitoring the AMQ queues and there is no pending
Are your consumers keeping up with your producers? One easy way to run out
of memory is to produce messages faster than you consume them.
Tim
On Mon, Nov 25, 2019, 11:16 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> Have you configured limits on memory usage in the broker
Have you configured limits on memory usage in the broker settings? You need
to look at a heap dump and see exactly where the memory is being used (if
it's messages on a destination, in prefetch etc).
Some general info about OOM and how to prevent it:
We have LiveTransfer application that use ActiveMQ to transfer data from
Production database to operational Database
Application is getting issue for every 50+ days i.e. OutOfMemoryError in
activeMQ and LT gets stopped. After restarting the AMQ services, it will
resume the transfer.
INFO |
10 matches
Mail list logo
