qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rupert Smith (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-531) [Memory Leak] Broker retains messages that are consumed with NO_ACK
Date Wed, 19 Sep 2007 13:44:43 GMT

    [ https://issues.apache.org/jira/browse/QPID-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528765
] 

Rupert Smith commented on QPID-531:
-----------------------------------

Martin, have you figured out a way to reproduce the problem? Did I just not run the NO_ACK
test for long enough to show this one up?

> [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
>
>
> 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.


Mime
View raw message