Bug 1254955 - qpidd does not support 'null source lookup' of existing links (used during JMS client durable subscription unsubscribe)
qpidd does not support 'null source lookup' of existing links (used during JM...
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
3.2
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: messaging-bugs
Messaging QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-19 06:11 EDT by Robbie Gemmell
Modified: 2018-03-06 15:40 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Known Issue
Doc Text:
In this release of the product, the JMS method +Session.unsubscribe(String)+ does not work when using the 10 JMS client and +qpidd+. This is because +qpidd+ does not handle an attach with the link name but no source, even if the link name is for a durable subscriber. As a workaround, subscriptions can be deleted manually using `qpid-config` or programmatically using another client.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Robbie Gemmell 2015-08-19 06:11:09 EDT
When an application calls "session.unsubscribe(<subscription-name>)" the JMS client opens a link with that name and a null Source, expecting the broker to either reject the attach (i.e reply attach with null source) if the link/subscription does not exist or attach it with the actual Source details if it does as detailed in the AMQP spec. It appears the broker always rejects the attach, so things may fail if they call unsubscribe to cleanup an existing subscription.

Note You need to log in before you can comment on or make changes to this bug.