Reputation: 226
Am feeding json data to scatter gatherer and sending messages to two message chunk splitters after transforming one copy to csv data and another to fixed length and setting "enable correlation id" to "always" option. But mule message chunk splitter is setting same Mule_Correlation_id to both the json and csv data and in turn which is same as normal "correlation_id" don't understand why this happens even though I am setting enable correaltion id to "always" option. here is the screen shot of the flow.
above is the screen shot of the mule flow . here is the settings of message chunk splitter
is there any thing I need to change to get different "mule_correlation_id".
Upvotes: 0
Views: 103
Reputation: 25709
The Mule 3.x splitter documentation mentions that it sets the following outbound properties:
All the parts splitted from the same original message will share the same MULE_CORRELATION_ID, so they can be related together. Each part should have a unique MULE_CORRELATION_SEQUENCE within the same MULE_CORRELATION_ID.
Upvotes: 1