activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <>
Subject [jira] Commented: (AMQ-735) Possible 4.0 consumer client memory leak?
Date Wed, 12 Jul 2006 18:16:51 GMT
    [ ] 

Niclas Hedhman commented on AMQ-735:

Does that mean ActiveMQ will also not throw away acknowledged messages and hold them around
as well?

We are looking at a 1 message per 2 seconds which are consumed in milliseconds, and yet (in
4.0.1) we are running out of memory. That is true for transacted/non-transacted as well as
auto-acknowledge and client-acknowledge. 
However, we also see that Lingo has no such problems, so perhaps we should try to look into
the Lingo sources to check how it uses ActiveMQ. Any pointer?

Btw, not sure if spring-jms throws anything particular into the mix either...

> 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
>     Assignee: james strachan
>     Priority: Critical
>      Fix For: 4.0.1
>  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