Petals CDK

Mismatch between consumer and provider with sendAsync

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 5.4.3, 5.5.0
  • Fix Version/s: 5.4.4, 5.6.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    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.

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

Activity

Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
53s
1
Victor NOËL
Wed, 27 Jan 2016 - 16:31:46 +0100
Open Open In Progress In Progress
3s
1
Victor NOËL
Wed, 27 Jan 2016 - 16:31:49 +0100
In Progress In Progress Resolved Resolved
59m 23s
1
Victor NOËL
Wed, 27 Jan 2016 - 17:31:12 +0100
Resolved Resolved Open Open
19h 46m
1
Victor NOËL
Thu, 28 Jan 2016 - 13:17:51 +0100
Open Open In Progress In Progress
1m 14s
1
Victor NOËL
Thu, 28 Jan 2016 - 13:19:05 +0100
In Progress In Progress Resolved Resolved
2h 5m
1
Victor NOËL
Thu, 28 Jan 2016 - 15:24:05 +0100

People

Dates

  • Created:
    Wed, 27 Jan 2016 - 16:30:53 +0100
    Updated:
    Fri, 29 Jan 2016 - 12:06:31 +0100
    Resolved:
    Thu, 28 Jan 2016 - 15:24:05 +0100