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

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

Show
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.
Hide
Christophe DENEUX added a comment - Fri, 29 Jan 2016 - 12:06:31 +0100

Backported in branch 4.3.x with svn#39001

Show
Christophe DENEUX added a comment - Fri, 29 Jan 2016 - 12:06:31 +0100 Backported in branch 4.3.x with svn#39001

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