activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feng Wang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-735) Possible 4.0 consumer client memory leak?
Date Thu, 08 Jun 2006 15:04:51 GMT
    [ https://issues.apache.org/activemq/browse/AMQ-735?page=comments#action_36261 ] 

Feng Wang commented on AMQ-735:
-------------------------------


I profiled DumpDumpJMSMsg.java because that is the one will throw "out of memory" error very
quickly.

I have attached the image for the instance count (instance.png).  As you can see, byte array
took the most of memory. But the counts of MessageDispatch, ActiveMQObjectMessage  and MessageId
keep increasing.  In the previouslyploaded pictures,
there was a loop in MessageDispatch reference graph.   Usually it is a sign of memory leak.


I guess that in Release 4  you start to use concurrent packge from emory universiy (but not
RC2 build). CopyOnWriteArrayList 
is from concurrent package and take a look at middle.png. CopyOnWriteArrayList has a reference
to object[1]. 

Since I am quite new to ActiveMQ  and emory  concurrent package (only 2 days), I am not sure
where the problem is. 







> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>
>          Key: AMQ-735
>          URL: https://issues.apache.org/activemq/browse/AMQ-735
>      Project: ActiveMQ
>         Type: Bug

>   Components: JMS client
>     Versions: 4.0
>  Environment: windows xp pro, jdk 1.5, AMQ 4.0 (incubator)
>     Reporter: Karthik Sethuraman
>     Priority: Critical
>  Attachments: activemq_735.zip, jmsmon.zip
>
>
> On running the attached test programs (one producer on a topic, one consumer on a topic),
the consumer eventually encounters OutOfMemoryError after receiving around 64 MB of messages).
Default JVM heap size is used (64 MB).
> The problem does not happen with RC2 build.
>  The test programs allows specification of message payloads of different sizes and different
message rates, as well number of  producer/consumer threads/instances., topics and topic connection
factories, via user environment variables.
> http://www.nabble.com/4.0+Consumer+OutOfMemoryError+bug--t1707655.html#a4660556

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message