You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2018/11/20 21:57:00 UTC
[jira] [Comment Edited] (QPIDJMS-434) Consumer whose close was
deferred in a client ack session can cause an exception when another
consumer is also present in that session
[ https://issues.apache.org/jira/browse/QPIDJMS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693826#comment-16693826 ]
Timothy Bish edited comment on QPIDJMS-434 at 11/20/18 9:56 PM:
----------------------------------------------------------------
Changes for this issue (QPIDJMS-257) allow this behaviour to happen.
was (Author: tabish121):
Changes for this issue allow this behaviour to happen.
> Consumer whose close was deferred in a client ack session can cause an exception when another consumer is also present in that session
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-434
> URL: https://issues.apache.org/jira/browse/QPIDJMS-434
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.38.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Major
> Fix For: 0.39.0
>
>
> When a consumer that has received but not acknowledged messages in a client ack session is closed, the close operation is deferred until either a message.acknowledge call is made or the parent session is closed. If there are two consumers in such a session a call to acknowledge on a message can lead to an exception being thrown in error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org