When there is two sendSync 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 a mismatch will happen in the DeliveryChannel implementation between them and provokes incoherent situations.
We should properly differentiate them in the code to avoid that.
When there is two sendSync 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 a mismatch will happen in the DeliveryChannel implementation between them and provokes incoherent situations.
We should properly differentiate them in the code to avoid that.
See also PETALSCDK-159.
Victor NOËL added a comment - Thu, 28 Jan 2016 - 13:26:44 +0100
This does not concerns Petals 4.3 because sendSync takes into account back-and-forth for the same exchange differently than implementation in trunk in local mode (and with NIO there is no problem).
Victor NOËL added a comment - Thu, 28 Jan 2016 - 13:26:44 +0100 This does not concerns Petals 4.3 because sendSync takes into account back-and-forth for the same exchange differently than implementation in trunk in local mode (and with NIO there is no problem).
This does not concerns Petals 4.3 because sendSync takes into account back-and-forth for the same exchange differently than implementation in trunk in local mode (and with NIO there is no problem).