[
https://issues.apache.org/jira/browse/QPIDJMS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941170#comment-14941170
]
ASF subversion and git services commented on QPIDJMS-116:
---------------------------------------------------------
Commit 301e32d69552bc183fadee471c45a1717a6347f1 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=301e32d ]
QPIDJMS-118, QPIDJMS-116: ensure the loop checks the expected conditions have
been satisified before continuing, ensure we actually wait for the given
timeout where appropriate
> 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]
