[jira] Commented: (QPID-531) [Memory Leak] Broker retains messages that are consumed with NO_ACK

["Rupert Smith (JIRA)" <qp...@incubator.apache.org>]

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

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

I'm trying to reproduce this independantly with the performance tests. I set up a pub/sub 1:10 ping test with no ack mode:

./Ping-Once-Async.sh -c[8] -s[1000] -d1D ackMode=257 pubsub=true destinationCount=10 messageSize=256 transacted=false

And letting it run. No out of memory error encountered in the first 5 minutes. Still running...

> [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: Rupert Smith
>             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.