Bug 489009 - [RFE] Message Id should be propagated to messages carod sends
Summary: [RFE] Message Id should be propagated to messages carod sends
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: 1.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: 1.2
: ---
Assignee: Robert Rati
QA Contact: Martin Kudlej
URL:
Whiteboard:
Depends On: 522467
Blocks: 527551
TreeView+ depends on / blocked
 
Reported: 2009-03-06 17:48 UTC by Matthew Farrellee
Modified: 2009-12-03 09:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Grid enhancement Messages produced by carod now carry the same MessageId as exists in work submitting AMQP messages. This will assist in correlation by submitter.
Clone Of:
Environment:
Last Closed: 2009-12-03 09:19:07 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2009:1633 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging and Grid Version 1.2 2009-12-03 09:15:33 UTC

Description Matthew Farrellee 2009-03-06 17:48:50 UTC
condor-low-latency-1.0-10.el5
condor-job-hooks-common-1.0-5.el5

A submitter of work via AMQP must set a MessageId to a unique value. It is used internally, by carod, to track messages.

The messages that carod produces while processing the work, e.g. status reject completion messages, do not carry a MessageId.

They should carry the same MessageId as the work, to assist in correlation by submitter.

Comment 1 Robert Rati 2009-03-19 17:36:13 UTC
Response messages from the low-latency daemon newo set a uuid for the message id and set the correlation id to the message id from the work being processed.

Fixed in:
condor-low-latency-1.0-13

Comment 3 Irina Boverman 2009-10-28 17:55:50 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Carod produced messages now carry the same MessageId as in work submitting AMQP messages, to assist in correlation by submitter (489009)

Comment 4 Lana Brindley 2009-11-05 02:10:50 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1,3 @@
-Carod produced messages now carry the same MessageId as in work submitting AMQP messages, to assist in correlation by submitter (489009)+Grid enhancement
+
+Messages produced by carod now carry the same MessageId as exists in work submitting AMQP messages. This will assist in correlation by submitter.

Comment 5 Martin Kudlej 2009-11-06 13:19:44 UTC
Tested on RHEL 5.4 x86_64 with condor-low-latency-1.0-9.el5 and condor-job-hooks-common-1.0-5.el5 and it doesn't work.
Tested on RHEL 5.4/4.8 x i386/x86_64 with condor-low-latency-1.0-21 and condor-job-hooks-1.0-13 and Message ID and Correlation ID were there.
-->VERIFIED

Comment 7 errata-xmlrpc 2009-12-03 09:19:07 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1633.html


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