Yes, it would be helpful to have your exact configuration, and to know the version of ActiveMQ that you are using.
Unfortunately I won't have time to try to reproduce this until the weekend. But in the meantime would you please try the following to see if we can narrow in on what aspect of the broker is the one using the memory? 1. Remove your Camel routes from your activemq.xml and restart, and see if the steady-state heap utilization changes. 2. Change activemq.xml to point to an empty or non-existent data directory and restart, and see if the steady-state heap utilization changes. 3. If neither of those show any reduction in heap usage, could you capture a CPU sampling from JVisualVM as I described in my first post from yesterday? Thanks, Tim On Tue, Apr 14, 2020, 7:06 AM hfridhi <[email protected]> wrote: > I agree with you the fact that we have to give the needed memory and do a > good sizing in order to avoid such problems. > However, my question is quite simple how it is possible that broker uses > around 1,3G after 18 seconds knowing that there is no message in queues. > < > http://activemq.2283324.n4.nabble.com/file/t379890/VisualVM_ActiveMQ_Uptime_20200414.jpg> > > PLease let me know if you require any configuration file. > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
