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

Ascending order - Click to sort in descending order
Victor NOËL made changes - Wed, 27 Jan 2016 - 16:31:46 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Critical [ 2 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Wed, 27 Jan 2016 - 16:31:49 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Wed, 27 Jan 2016 - 17:31:12 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.6.0 [ 10611 ]
Resolution Fixed [ 1 ]
Victor NOËL made changes - Wed, 27 Jan 2016 - 17:31:34 +0100
Description 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. 		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.
Hide
Permalink
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.
Victor NOËL made changes - Thu, 28 Jan 2016 - 13:17:51 +0100
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Victor NOËL made changes - Thu, 28 Jan 2016 - 13:18:10 +0100
Affects Version/s 5.4.3 [ 10501 ]
Victor NOËL made changes - Thu, 28 Jan 2016 - 13:19:05 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Thu, 28 Jan 2016 - 15:24:05 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.4.4 [ 10614 ]
Resolution Fixed [ 1 ]
Hide
Permalink
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
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
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.