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.
--> [EMAIL PROTECTED] (91
bytes)
(field transportListener:)
--> [EMAIL PROTECTED] (56
bytes)
(field transportListener:)
--> [EMAIL PROTECTED]
(44 bytes)
(field transportListener:)
--> org.apache.activemq.transport.failover.FailoverTransport
[EMAIL PROTECTED]
(12 bytes) (field this$0:)
-->
[EMAIL PROTECTED]
(97
bytes) (field stateTracker:)
--> [EMAIL PROTECTED] (17
bytes)
(field connectionStates:)
-->
edu
.emory
[EMAIL PROTECTED]
(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
[EMAIL PROTECTED]
(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
[EMAIL PROTECTED]
(24 bytes) (field value:)
--> [EMAIL PROTECTED] (28 bytes)
(field
transactions:)
-->
edu
.emory
[EMAIL PROTECTED]
(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
[EMAIL PROTECTED]
(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
[EMAIL PROTECTED]
(24 bytes) (field next:)
-->
edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap
[EMAIL PROTECTED]
(24 bytes) (field value:)
--> [EMAIL PROTECTED] (25 bytes)
(field
commands:)
--> [EMAIL PROTECTED] (20 bytes) (field elementData:)
--> [Ljava.lang.Object;@0x693107a8 (48 bytes) (Element 0 of
[Ljava.lang.Object;@0x693107a8:)
--> [EMAIL PROTECTED]
(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.
