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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.6.0
• Component/s: qpid-jms-client
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 22/Sep/15 13:34
• Updated: 06/Jan/16 12:33
• Resolved: 08/Oct/15 16:47

Description

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.