You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Feng Wang (JIRA)" <ji...@apache.org> on 2006/06/07 23:52:51 UTC

[jira] Updated: (AMQ-735) Possible 4.0 consumer client memory leak?

     [ https://issues.apache.org/activemq/browse/AMQ-735?page=all ]

Feng Wang updated AMQ-735:
--------------------------

    Attachment: activemq_735.zip

> 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