Jörg,
I finally did some analysis with yourkit today and indeed there is a
memory leak, I captured the issue and resolution with reference to
this thread in the issue:
https://issues.apache.org/activemq/browse/AMQ-2143
I think the resolution of the leak should help with more stable
enqueue rates.
Hi Gary,
we just made a new test which startet yesterday.
JVM settings of AMQ where 3 GB heap size.
We send about 800 msg / sec into the queue, the size was limited to 3 GB.
During that time sending messages to the queue got slower and slower. Even
after the queue was full and new messages have
Hi Jörg,
I did some analysis of the per message allocations from your email. It
is clear that each store write allocates a bunch of objects, however,
from code inspection, I cannot see a point where they are leaked
through a reference.
There are two relevant points that may make static analysis a l
Hello,
I just tried something with the Netbeans memory profiler.
My assumption is:
If nothing hass been added to an application then after 2 full runs of the
Garbace Collector the memory should be the same.
In the past we have seen that memory was increasing while messages have been
processed by
Btw:
These are my JVM settings (1.6.0_10)
# Java Additional Parameters
# note that n is the parameter number starting from 1.
wrapper.java.additional.1=-Dactivemq.home=%ACTIVEMQ_HOME%
wrapper.java.additional.2=-Dactivemq.base=%ACTIVEMQ_BASE%
wrapper.java.additional.3=-Dcom.sun.management.jmxremote
