CODEWITHSUNDEEP
mule
rewolf
rewolf

Reputation: 5871

Persist Correlation Id through HTTP requests

In my mule flow the CorrelationId is set on the message, but after making an outbound http:request, the message loses the Correlation Id.

What is the correct way to prevent the Cid being lost?

UPDATE

No matter what I tried, the CorrelationId is always lost. I've created a JIRA issue demonstrating the difference in behaviour between http:outbound-endpoint and http:request https://www.mulesoft.org/jira/browse/MULE-8522 I don't believe the CorrelationId is supposed to be lost in this case.

Upvotes: 3

Views: 1432

Answers (1)

Anirban Sen Chowdhary
Anirban Sen Chowdhary

Reputation: 8311

You can set the corrolation id in the message outbound so that it is available in external flow.

You can also look into the example to add Corrolation id in your message before sending to a outbound endpoint :- http://blogs.mulesoft.org/total-traceability/

UPDATE

Then use message enricher which wrapp the HTTP request component and by that way you can get the value from the external service without disturbing your actual payload and existing corrolation id http://www.mulesoft.org/documentation/display/current/Message+Enricher

Upvotes: 2

Related Questions