Red Hat Bugzilla – Bug 488116
JMS client doesn't handle exception during subscribe correctly
Last modified: 2015-11-15 19:06:51 EST
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).
Tested on RHEL 5.3/4.7 i386/x86_64 and it works as expected --> VERIFIED
Fixed and verified; closing.