Bellow is result from Eclipse Memory Analyzer *Problem Suspect 1* One instance of "com.sun.jmx.mbeanserver.JmxMBeanServer" loaded by "<system class loader>" occupies 182,127,056 (57.45%) bytes. The instance is referenced by org.apache.activemq.broker.jmx.ManagementContext @ 0xf142bc0 , loaded by "java.net.URLClassLoader @ 0xef3bad0". The memory is accumulated in one instance of "java.util.HashMap$Entry[]" loaded by "<system class loader>".
*Problem Suspect 2* 74,663 instances of "javax.management.ObjectName", loaded by "<system class loader>" occupy 62,369,904 (19.67%) bytes. These instances are referenced from one instance of "java.lang.Object[]", loaded by "<system class loader>" *Possible Memory Waste* Duplicate Strings Found 146 occurrences of char[] with at least 10 instances having identical content. Total size is 8,593,000 bytes. Top elements include: •22 × \u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u... (59,338 bytes) •4,355 × JMS Client id of the Connection the Producer is on... (120 bytes) •4,355 × User Name used to authorize creation of this Produ... (120 bytes) •4,355 × The name of the destionation the Producer is on. (112 bytes) •4,355 × Is the producer configured for Async Dispatch (104 bytes) -- View this message in context: http://activemq.2283324.n4.nabble.com/Memory-Leak-problem-after-upgrade-from-5-5-1-to-5-10-tp4685103p4685201.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
