[
https://issues.apache.org/jira/browse/QPID-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171218#comment-15171218
]
Keith Wall commented on QPID-7115:
----------------------------------
I think the logs point to a client problem rather than a broker. The logs show
that the message was received by the session just before the consumer was
closed, but no message release was ever sent. I think you can infer from the
logging that the message was neither of the session's _queue or the consumer's
queue when the consumer closed was process. This makes me think that the
message was actually in flight through the dispatcher at the moment. However, a
race here should be prevented by the message delivery lock. I cannot
currently explain how this problem occurred.
> Closing a consumer may not release all messages
> -----------------------------------------------
>
> Key: QPID-7115
> URL: https://issues.apache.org/jira/browse/QPID-7115
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: qpid-java-6.1
> Reporter: Keith Wall
> Attachments:
> TEST-org.apache.qpid.test.unit.close.MessageConsumerCloseTest.testPrefetchedMessagesReleasedOnConsumerClose.txt
>
>
> A failure of
> MessageConsumerCloseTest#testPrefetchedMessagesReleasedOnConsumerClose showed
> that on 0-10, closing a consumer does not always release all messages that
> have been sent to that consumer. The message remained stuck in the client,
> and would have remained there until the client disconnected or closed its
> session.
> See the attached log.
--
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
