Petals ESB Container

Mismatch between consumer and provider with sendSync

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 5.0.0
  • Fix Version/s: 5.0.1
  • Component/s: Router
  • Security Level: Public
  • Description:
    Hide

    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.

    Show
    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.
  • Environment:
    -

Activity

Hide
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).

Show
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).

People

Dates

  • Created:
    Wed, 27 Jan 2016 - 17:23:19 +0100
    Updated:
    Thu, 28 Jan 2016 - 13:26:44 +0100
    Resolved:
    Wed, 27 Jan 2016 - 17:31:44 +0100