[
https://issues.apache.org/jira/browse/QPID-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415456#comment-15415456
]
Gordon Sim commented on QPID-5337:
----------------------------------
I think I didn't feel a strong urge to commit it as there is an obvious
workaround (i.e. ack the messages regardless). It didn't seem to be causing a
great deal of pain. I also got no reviews of my patch. I'd be inclined to just
close this now. What we should do is figure out what the future of
qpid.messaging in python is. It doesn't support 1.0, is it now deprecated? If
so should we (or do we already) say that clearly?
> Memory leak in python client - unacked messages kept when no accept is
> necessary
> --------------------------------------------------------------------------------
>
> Key: QPID-5337
> URL: https://issues.apache.org/jira/browse/QPID-5337
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.22
> Environment: RHEL 6.4
> Reporter: Renier Morales
> Assignee: Gordon Sim
> Labels: memory-leak, performance
>
> We have found with python-qpid-0.22 that you have to acknowledge all messages
> received, even if you have subscribed using mode:browse (where ack does not
> apply) or even if you have subscribed to an unreliable topic exchange (where
> ack is not needed).
> In these cases, if you don't acknowledge the messages received, memory is
> leaked, due to the accumulation of messages in an internal unacked list at
> the client.
> More information at this qpid-users mailing list thread:
> http://qpid.2158936.n2.nabble.com/Use-of-mode-browse-and-session-acknowledge-in-topic-exchanges-td7600571.html#a7600642
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
