[
https://issues.apache.org/jira/browse/QPIDJMS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947727#comment-14947727
]
ASF subversion and git services commented on QPIDJMS-116:
---------------------------------------------------------
Commit 9fe2d741056cee53346c5f42e1dae5cbfcff1c02 in qpid-jms's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=9fe2d74 ]
QPIDJMS-116 Attempt to fix the sporadic test failure of timed received
after connection drop. On connection loss the session is shutdown which
first stops itself and its consumers before in turn shutting down the
consumers and setting a failure cause. This can result in the consumer
dequeue from the prefetch buffer returning but not having a set failure
cause yet and then return null because it has subsequently been
shutdown.
> make behaviour of receive and receiveNoWait consistent when consumer closes
> due to a problem
> --------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-116
> URL: https://issues.apache.org/jira/browse/QPIDJMS-116
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.5.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.6.0
>
>
> Currently, if a consumer clsoes due to a problem, recieveNoWait will throw an
> exception, but a blocking receive in progress will return null. The behaviour
> should be consistent, and throwing the exception seems reasonable given that
> returning null would likely just lead to future use of the consumer which
> will itself then throw an exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
