Do you have a significant number of unconsumed persistent messages? Especially on many queues/topics? That would produce an increase in the amount of RAM relative to an empty broker, because the broker will pull a certain number of the messages into memory to be ready to dispatch them to consumers without a disk read.
Also, I've never used embedded Camel routes, so I'm not sure what to expect from them in terms of memory usage. One other technique you could use is to capture a CPU sample via JVisualVM during the time period when the memory usage is increasing, to determine which broker activities are likely causing the increase. Tim On Tue, Apr 14, 2020, 2:33 AM hfridhi <haythem.fri...@gmail.com> wrote: > Hello Tim, > Thank you for your quick reply. > I agree with that increasing JVM's heap is a desperate measures in > desperate > times but my question is why even after a restart memory is quickly > consumed > (a window of 2 minutes). > < > http://activemq.2283324.n4.nabble.com/file/t379890/VisualVM_ActiveMQ_20200414.jpg> > > > PS: yesterday I was passing around 508K message through the broker. But why > is possible that after restarting, JVM's heap is reached within 2 minutes > without any activity? > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
