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 you the GC strategy in use; if not, you can find the default in your JVM's documentation.
Either way, if you're at 90+%, the GC is probably using most of the CPU trying unsuccessfully to free up memory, which will make the broker considerably less responsive. So what Producer Flow Control limits have you put in place on the broker to limit the amount of memory used by messages in the memory store? If you haven't configured those, you probably need to do so. (Details of how to do it and what options are available are on the wiki.) Tim On Jan 31, 2018 12:54 AM, "tejas13" <tejas.sawa...@tcs.com> wrote: > 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 >
