activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Davies <rajdav...@gmail.com>
Subject Re: ActiveMQ 4.11 Memory Leak?
Date Tue, 05 Feb 2008 19:37:37 GMT
It will is difficult to determine without more information - is it  
possible to generate a test case ?

On Feb 5, 2008, at 6:34 PM, greenbean wrote:

>
> We have suddenly run into a problem with our server running out of  
> heap
> space.  When I look at the hprof file generated, I see alot of  
> activemq data
> hanging around.  Is this normal?  It almost looks like the messages  
> are not
> getting garbage collected after sent.  This worked fine in the  
> past.  We
> have not change anything recently except for deploying some new  
> application
> code.  Any ideas what could cause this?
>
> Here is a snip from JHAT showing a reference to an  
> ActiveMQObjectMessage.
> There are lots of these.
>
> --> org.apache.activemq.transport.tcp.TcpTransport@0x5fc5c078 (91  
> bytes)
> (field transportListener:)
> --> org.apache.activemq.transport.InactivityMonitor@0x5fc5c040 (56  
> bytes)
> (field transportListener:)
> --> org.apache.activemq.transport.WireFormatNegotiator@0x5fc5c010  
> (44 bytes)
> (field transportListener:)
> --> org.apache.activemq.transport.failover.FailoverTransport 
> $1@0x5fc687f8
> (12 bytes) (field this$0:)
> -->  
> org.apache.activemq.transport.failover.FailoverTransport@0x5fc4b8e0  
> (97
> bytes) (field stateTracker:)
> --> org.apache.activemq.state.ConnectionStateTracker@0x5fc4ba58 (17  
> bytes)
> (field connectionStates:)
> -->
> edu 
> .emory 
> .mathcs.backport.java.util.concurrent.ConcurrentHashMap@0x5fc4ba70
> (44 bytes) (field segments:)
> -->
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $Segment;@0x5fc4baa0
> (72 bytes) (Element 11 of
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $Segment;@0x5fc4baa0:)
> -->
> edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $Segment@0x5fc4bbf0
> (32 bytes) (field table:)
> -->
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry;@0x5fc4bc20
> (12 bytes) (Element 0 of
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry;@0x5fc4bc20:)
> -->
> edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry@0x5fc4bc30
> (24 bytes) (field value:)
> --> org.apache.activemq.state.ConnectionState@0x5fc4bcc8 (28 bytes)  
> (field
> transactions:)
> -->
> edu 
> .emory 
> .mathcs.backport.java.util.concurrent.ConcurrentHashMap@0x5fc4bd90
> (44 bytes) (field segments:)
> -->
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $Segment;@0x5fc4bdc0
> (72 bytes) (Element 9 of
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $Segment;@0x5fc4bdc0:)
> -->
> edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $Segment@0x5fc4bf30
> (32 bytes) (field table:)
> -->
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry;@0xb38b02e8
> (2056 bytes) (Element 89 of
> [Ledu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry;@0xb38b02e8:)
> -->
> edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry@0xbd7155a8
> (24 bytes) (field next:)
> -->
> edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap 
> $HashEntry@0x8dbed698
> (24 bytes) (field value:)
> --> org.apache.activemq.state.TransactionState@0x69310770 (25 bytes)  
> (field
> commands:)
> --> java.util.ArrayList@0x69310790 (20 bytes) (field elementData:)
> --> [Ljava.lang.Object;@0x693107a8 (48 bytes) (Element 0 of
> [Ljava.lang.Object;@0x693107a8:)
> --> org.apache.activemq.command.ActiveMQObjectMessage@0x69310808  
> (162 bytes)
> -- 
> View this message in context: http://www.nabble.com/ActiveMQ-4.11-Memory-Leak--tp15296611s2354p15296611.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


Mime
View raw message