Le 11-07-13 10:11, Dejan Bosanac a écrit : > can you test the latest release 5.5.0 (or the latest 5.6-SNAPSHOT) and > confirm that problem still exists?
I did some tests with 5.5.0 and it still exists. Heavy usage of JMX seems to be the source of the problem. The test I ran consisted of a nagios check that uses JMX to verify consumer count, persistence and heap/non-heap usage. Let me know if you need a heap dump or anything else. Regards, -- Simon-Pierre LeBel [iWeb] IT Architecture Specialist / Technical Lead Spécialiste de l'Architecture TI / Leader Technique http://www.iWeb.com/
