Bug 692901

Summary: Trace ID isn't appended properly if message trace already contains new trace ID via substring check
Product: Red Hat Enterprise MRG Reporter: Andy Goldstein <agoldste>
Component: qpid-cppAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.3CC: iboverma, jross
Target Milestone: ---Keywords: TestCaseProvided
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 698367, 803771    
Attachments:
Description Flags
Test case none

Description Andy Goldstein 2011-04-01 14:53:09 UTC 
Description of problem: the broker does not append a new trace ID to a message if the message's trace already includes the new trace ID when it's a substring of the existing trace.

For example:
- q1 has a trace id of Test12
- q2 has a trace id Test1

Send message to q1
    It will get a trace of Test12

Retrieve message from q1

Modify retrieved message's routing key so that it's now sent to q2 (keep the trace field intact)

Send message to q2
    Message trace will remain Test12 instead of being Test12,Test1

It appears that the broker does a substring match on the new trace (Test1), and, if found, does not add this as a new trace to the message.


Version-Release number of selected component (if applicable):qpid-cpp-server-0.7.946106-28.el5

How reproducible:100%

Steps to Reproduce: see attached python script
Comment 1 Andy Goldstein 2011-04-01 14:53:53 UTC 
Created attachment 489420 [details]
Test case