You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/01/10 10:12:34 UTC
[jira] Updated: (QPID-531) [Memory Leak] Broker retains messages
that are consumed with NO_ACK
[ https://issues.apache.org/jira/browse/QPID-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-531:
--------------------------------
Fix Version/s: (was: M2)
M2.1
> [Memory Leak] Broker retains messages that are consumed with NO_ACK
> -------------------------------------------------------------------
>
> Key: QPID-531
> URL: https://issues.apache.org/jira/browse/QPID-531
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: M2.1
>
>
> When testing consuming messages via NO_ACK the broker continually OOMEd. Switching to AUTO_ACK cleared things up.
> Looks like that the broker, while dequeing NO_ACK msgs is not allowing them to be gc'd. May be due to the way the Queue and the PDQ interact. Messages were being sent to a Topic and consumed by a two clients.
> Running two sustained.TestClient
> - Producer
> - Consumer
> and a sustained.TestCoordinator with -DackMode=257 (for no_ack) should cause the broker to fail fairly quickly.
> More docs on this test can be found on the wiki: http://cwiki.apache.org/qpid/sustained-tests.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.