Bug 692901 - Trace ID isn't appended properly if message trace already contains new trace ID via substring check
Summary: Trace ID isn't appended properly if message trace already contains new trace ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 698367 803771
TreeView+ depends on / blocked
 
Reported: 2011-04-01 14:53 UTC by Andy Goldstein
Modified: 2021-03-16 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Test case (1.92 KB, text/x-python-script)
2011-04-01 14:53 UTC, Andy Goldstein 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.