cause: federation routes tag messages as part of loop prevention; the tagging of a message that is to be delivered down multiple such routes can result in the modification of the message concurrent with its encoding
consequence: the concurrent modification can cause wire level protocol violation or segmentation faults
fix: clone messages before adding the tag to them tp prevent concurrent modification as they are being delivered and encoded
result: a message travelling down such routes will now only have the tag of one path added to it (previously it could have included tags from some or all of the other matching routes)
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
cause: federation routes tag messages as part of loop prevention; the tagging of a message that is to be delivered down multiple such routes can result in the modification of the message concurrent with its encoding
consequence: the concurrent modification can cause wire level protocol violation or segmentation faults
fix: clone messages before adding the tag to them tp prevent concurrent modification as they are being delivered and encoded
result: a message travelling down such routes will now only have the tag of one path added to it (previously it could have included tags from some or all of the other matching routes)
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/RHSA-2010-0756.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: cause: federation routes tag messages as part of loop prevention; the tagging of a message that is to be delivered down multiple such routes can result in the modification of the message concurrent with its encoding consequence: the concurrent modification can cause wire level protocol violation or segmentation faults fix: clone messages before adding the tag to them tp prevent concurrent modification as they are being delivered and encoded result: a message travelling down such routes will now only have the tag of one path added to it (previously it could have included tags from some or all of the other matching routes)