When there is two sendAsync from the same component concerning the same exchange (one acting as a provider and the other as a consumer, most certainly in two different SUs), then the AsyncContext of the second call to sendAsync will overwrite the AsyncContext of the other and provokes incoherent situations.
We should properly differentiate them in the code to avoid that.
When there is two sendAsync from the same component concerning the same exchange (one acting as a provider and the other as a consumer, most certainly in two different SUs), then the AsyncContext of the second call to sendAsync will overwrite the AsyncContext of the other and provokes incoherent situations.
We should properly differentiate them in the code to avoid that.
See also PETALSESBCONT-394.
Victor NOËL added a comment - Thu, 28 Jan 2016 - 13:17:51 +0100 Reopening for Petals 4.3 (CDK 5.4.3): this only impacts EIP, Camel and Activiti because only them use sendAsync.
Reopening for Petals 4.3 (CDK 5.4.3): this only impacts EIP, Camel and Activiti because only them use sendAsync.