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

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
7s
1
Victor NOËL
Wed, 27 Jan 2016 - 17:23:26 +0100
Open Open In Progress In Progress
2s
1
Victor NOËL
Wed, 27 Jan 2016 - 17:23:28 +0100
In Progress In Progress Resolved Resolved
8m 16s
1
Victor NOËL
Wed, 27 Jan 2016 - 17:31:44 +0100

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
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.