[
https://issues.apache.org/activemq/browse/AMQ-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57751#action_57751
]
Rob Davies commented on AMQ-1974:
---------------------------------
Ryan - your issues looks like
https://issues.apache.org/activemq/browse/AMQ-2475 - which is fixed in 5.3.1
and 5.4
> MemoryUsage stays at 100% used forever after all messages are sent
> ------------------------------------------------------------------
>
> Key: AMQ-1974
> URL: https://issues.apache.org/activemq/browse/AMQ-1974
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Environment: Linux with 2.6.18 kernel
> JDK 1.5.0_15
> Reporter: Neal Yin
> Priority: Critical
> Fix For: 5.4.0
>
> Attachments: MsgsPerSecond.diff, TryJmsClient.java, TryJmsManager.java
>
>
> We use a network of brokers and topic to do messaging. All our message
> producers and consumers talk to the local VM broker. We reply on bridges
> between network of brokers to move messages between brokers. We found a case
> that MemoryUsage stays at 100% forever after all messages are sent.
> I attached two files to show this memory leak problem. TryJmsClient keeps
> sending persistent messages to a Topic. TryJmsManager has a message consumer.
> Start TryJmsManager first and then start TryJmsClient. After running about 10
> seconds, TryJmsClient stops sending because of getting "SystemUsage memory
> limit reached" error. About 24K messages are sent and consumer shows it get
> all messages. Now examine ActiveMQ MemoryUsage printout of TryJmsClient,
> MemoryUsage percentage stays at 100% or 99% forever. Producer can never send
> any more messages.
> Note1: If I slow down sending by adding a sleep, I don't see memory leak
> immediately. I am not sure for longer running time.
> Note2: If I use Queue instead of Topic, there is no memory leak.
> Note3: This looks like similar to AMQ-1833 that is fixed in 5.2. But after
> testing with 5.2 snapshot, I still get the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
