The JVM uses a GC strategy even if you don't explicitly pick one; that's
why you don't have to explicitly free your heap variables in Java like you
do in C++. It's probably Parallel if you haven't customized it, but you
should check that. If I recall correctly, JConsole and/or JVisualVM might
tell
Hello Team,
Thank you for reply.
We are not using any external GC mechanism.
We have allocated 8 GB memory. At the time of OOM greater than 90% memory
store is used.
Please help us.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
What garbage collection algorithm are you using? If it's CMS, it's possible
to get an OOM even though there is heap space still available.
What limits do you have configured on the memory store, and what percentage
is used shortly before the OOM occurs?
Tim
On Jan 22, 2018 3:51 AM, "tejas13" wr
Hello Team,
Last one year we are using Active MQ in production system.
We are using version 5.14.5
In early days we were facing max connection exceeded problem, we resolved
that by identifying unnecessary open connections.
Now we are facing one more problem, after each 10 to 15 days, active mq
