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.
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
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)
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.
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
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