You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2015/10/08 18:47:26 UTC

[jira] [Resolved] (QPIDJMS-116) make behaviour of receive and receiveNoWait consistent when consumer closes due to a problem

     [ https://issues.apache.org/jira/browse/QPIDJMS-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPIDJMS-116.
------------------------------------
    Resolution: Fixed

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org