Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1509058

Summary:	proton-c mixing up two links if one has a name that's a substring of the other
Product:	Red Hat Enterprise MRG	Reporter:	Mike Cressman <mcressma>
Component:	qpid-proton	Assignee:	Alan Conway <aconway>
Status:	CLOSED ERRATA	QA Contact:	Petr Matousek <pematous>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2	CC:	jross, pematous
Target Milestone:	3.2.7
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	qpid-proton-0.16.0-8	Doc Type:	Bug Fix
Doc Text:	Cause: Consequence: If a user creates a receiver using a queue name that is a prefix of a previously created receiver's name (on the same connection/session), the broker can return access to the wrong one. Fix: Result: The code was fixed so that access to the correct queue is ensured.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-20 16:52:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Cressman 2017-11-02 20:25:05 UTC

Description of problem:
If two links exist where one one has a name that is the substring of the other, proton can get confused, and may find the wrong one

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
See https://issues.apache.org/jira/browse/PROTON-1661
and https://issues.apache.org/jira/browse/PROTON-1466


Expected results:
Even when one link name is a substring of another, both can be found (i.e. via python client's create_receiver)

Additional info:

Comment 2 Petr Matousek 2017-11-09 19:59:24 UTC

This issue has been fixed. Internal test case has been linked and verified on all supported platforms. 

packages under test:
* qpid-proton-c-0.16.0-8
* qpid-cpp-1.36.0-13

-> VERIFIED

Comment 5 errata-xmlrpc 2017-11-20 16:52:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:3253