Bug 488116

Summary: JMS client doesn't handle exception during subscribe correctly
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-javaAssignee: Rafael H. Schloming <rafaels>
Status: CLOSED CURRENTRELEASE QA Contact: Frantisek Reznicek <freznice>
Severity: medium Docs Contact:
Priority: high    
Version: 1.1CC: esammons, jross, mkudlej, tross
Target Milestone: 1.1.1   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-29 18:47:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Modified version of pub-sub listener that uses a durable subscription none

Description Gordon Sim 2009-03-02 19:03:39 UTC
Created attachment 333776 [details]
Modified version of pub-sub listener that uses a durable subscription

If two connection using the same clientid both try to create a message consumer for the same durable subscription, the broker issues an exception to one of them (as the message.subscribe request has the exclusive flag set). However this does not result in the application receiving an exception; instead the request hangs and eventually times out waiting for 'completion'.

To reproduce run two instances of the attached listener (modified from the pubsusb example).

Comment 1 Martin Kudlej 2009-04-16 09:55:34 UTC
Tested on RHEL 5.3/4.7 i386/x86_64 and it works as expected --> VERIFIED

Comment 2 Justin Ross 2011-06-29 18:47:08 UTC
Fixed and verified; closing.