activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Commented: (AMQ-735) Possible 4.0 consumer client memory leak?
Date Thu, 08 Jun 2006 08:39:51 GMT
    [ ] 

james strachan commented on AMQ-735:

BTW if those numbers are not the number of instances in the JVM - which could be true (they
might be hashcodes rather than instance counts) - then the pictures are not helpful - we need
to know how many instances of each type there are - i.e. to find a memory leak we need to
know what objects are using up all the RAM

> Possible 4.0 consumer client memory leak?
> -----------------------------------------
>          Key: AMQ-735
>          URL:
>      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:,
> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message