Memory Leak problem after upgrade from 5.5.1 to 5.10

[edwin_wang <ed...@brocadesoft.com>]

Hi All
Our production environment has use ActiveMQ 5.5.1 for a long time without
problem. However, recently we want to upgrade to JAVA7. Therefore, I try to
use ActiveMQ 5.10. However, since I use the version 5.10, the ActiveMQ will
easy run into out of memory problem after several day.

I try to reproduce the problem. I use the same environment and same
configration for both 5.5.1 and 5.10. After several days, the 5.10 run into
out of memory while the 5.5.1 go well. 

I'm not sure whehter it is a problem of version 5.10 or I need to change any
configration after upgrade from 5.5.1 to 5.10? 

By the way, I have try to use JConsole to check the memory and found for
5.10 the problem is that the "Tenured Gen" will grow up and up until full.
And then JVM will do GC all the time and finally run into out of memory.
While, for 5.5.1 the "Tenured Gen" is well and can be successfully released
by full GC.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Memory-Leak-problem-after-upgrade-from-5-5-1-to-5-10-tp4685103.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

答复: Memory Leak problem after upgrade from 5.5.1 to 5.10

[edwin_wang <ed...@brocadesoft.com>]

OK，I will try to do this.

 

发件人: artnaseef [via ActiveMQ]
[mailto:ml-node+s2283324n4685126h61@n4.nabble.com] 
发送时间: 2014年8月29日 10:45
收件人: edwin_wang
主题: Re: Memory Leak problem after upgrade from 5.5.1 to 5.10

 

It's hard to know what's causing the problem from the description. 

Can you perform java memory-leak diagnosis? 

Capturing a heap dump after running for a while, or perhaps two with a few
hours between them, and then opening in your favorite heap-dump analysis
tool.  Yourkit is a good one for finding memory leaks.  VisualVM can do the
job, but can be harder to work through. 

Use the "calculate retained sizes" feature of such a tool to get a good feel
for the largest retainers of memory. 

  _____  

If you reply to this email, your message will be added to the discussion
below:

http://activemq.2283324.n4.nabble.com/Memory-Leak-problem-after-upgrade-from
-5-5-1-to-5-10-tp4685103p4685126.html 

To unsubscribe from Memory Leak problem after upgrade from 5.5.1 to 5.10,
click here
<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubs
cribe_by_code&node=4685103&code=ZWR3aW5fd2FuZ0Bicm9jYWRlc29mdC5jb218NDY4NTEw
M3wxMTAxMDE0Njg0> .
 
<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_
viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.Bas
icNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.templat
e.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant
_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> NAML






--
View this message in context: http://activemq.2283324.n4.nabble.com/Memory-Leak-problem-after-upgrade-from-5-5-1-to-5-10-tp4685103p4685128.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Memory Leak problem after upgrade from 5.5.1 to 5.10

[edwin_wang <ed...@brocadesoft.com>]

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.

Re: Memory Leak problem after upgrade from 5.5.1 to 5.10

[artnaseef <ar...@artnaseef.com>]

It's hard to know what's causing the problem from the description.

Can you perform java memory-leak diagnosis?

Capturing a heap dump after running for a while, or perhaps two with a few
hours between them, and then opening in your favorite heap-dump analysis
tool.  Yourkit is a good one for finding memory leaks.  VisualVM can do the
job, but can be harder to work through.

Use the "calculate retained sizes" feature of such a tool to get a good feel
for the largest retainers of memory.



--
View this message in context: http://activemq.2283324.n4.nabble.com/Memory-Leak-problem-after-upgrade-from-5-5-1-to-5-10-tp4685103p4685126.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.