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" <tejas.sawa...@tcs.com> wrote: > > 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 is > getting restarted automatically. Before restarting it goes into hang mode. > > Few findings from log analysis. > 1] JVM Hanged/Crashed > > 2] INFO | jvm 3 | java.lang.OutOfMemoryError: GC overhead limit > exceeded > INFO | jvm 3 | at > java.util.concurrent.CopyOnWriteArrayList.remove(Unknown > Source)[:1.7.0_80] > INFO | jvm 3 | | at > java.util.concurrent.CopyOnWriteArraySet.remove(Unknown Source)[:1.7.0_80] > > We have allocated 8 GB memory only for Active MQ. > > Please help us to resolve this issue. > > > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
