[
https://issues.apache.org/jira/browse/QPID-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193816#comment-17193816
]
Gordon Sim commented on QPID-8462:
----------------------------------
The purger will move expired messages to DELETED state. This means it does not
hold on to the message data. However the record within the queue structure is
still there. Using `qpid-stat -u` should show subscriptions with unacked
messages.
> Qpid broker memory increases when a receiver is paused with message pending
> acks
> ---------------------------------------------------------------------------------
>
> Key: QPID-8462
> URL: https://issues.apache.org/jira/browse/QPID-8462
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: qpid-cpp-1.39.0
> Environment: Linux
>
> Reporter: KALYANARAMAN SIVARAMAN
> Priority: Major
> Attachments: brokerMemoryIncrease.tar
>
>
> Given the situation where we have a receiver "Receiver1" acquire 1 message
> from a queue "ReceiverQueue" but if the message is not acknowledged and
> Receiver1 process is paused using kill -STOP <pidOfReceiver1>.
> Any further messages sent to ReceiverQueue is marked as DELETED even though
> we have another receiver "Receiver2" properly acquire messages from the queue
> and also sends acknowledgements, the broker memory linearly increases until
> all the memory in the box is used. Purger cleaning up messages does not help.
> Once we kill Receiver1 the broker memory stabilizes.
> All of the repro steps are automated in the attached reproducer.
>
> Please follow the steps to reproduce the issue
>
> Step 1: tar -xf brokerMemoryIncrease.tar
> Step 2: cd brokerMemoryIncrease
> Step 3: ./qpidRepro.sh
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
