Details
-
Type:
Patch submission
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.1.2
-
Fix Version/s: 3.1.4 (EE only), 3.2.2 (EE only)
-
Component/s: Transport: JMS
-
Labels:
-
User impact:High
-
Similar Issues:None
-
Effort:XS
Description
The jms: object-to-jmsmessage-transformer fails to set the correlation ID if it is contained in the inbound scope instead of the outbound scope (which probably is when the correlation ID has been set in a previous service).
The class org.mule.transport.jms.transformers. AbstractJmsTransformer iterates through all outbound properties and sets the correlationID when it reaches MULE_CORRELATION_ID_PROPERTY. The correlation ID doesn´t necessarily have to be defined as outbound property (which can also be seen in org.mule. DefaultMuleMessage#getCorrelationId()). I´ll attach a suggestion for a fix of this bug.
As temporary workaround one can add the correlation ID to the outbound scope using the following message-property-transformer:
<message-properties-transformer scope="outbound">
<add-message-property key="MULE_CORRELATION_ID" value="#[mule:message.correlationId]" />
</message-properties-transformer>
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | AbstractJmsTransformer.java [ 14405 ] | |
| Attachment | AbstractJmsTransformer.patch [ 14406 ] |
| Issue Type | Bug [ 1 ] | Patch submission [ 5 ] |
| Attachment | testcase-5838.zip [ 14510 ] |
| Priority | To be reviewed [ 6 ] | Critical [ 2 ] |
| Fix Version/s | New Backlog [ 11111 ] |
| Effort | XS |
| Assignee | Stephen Fenech [ stephenfenech ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Resolution | Fixed [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | New Backlog [ 11111 ] | |
| Fix Version/s | 3.2.2 (EE only) [ 11105 ] | |
| Fix Version/s | 3.1.4 (EE only) [ 11079 ] | |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
