Petals CDK

After a sendAsync has expired, the exchange is not owned by the sender

Details

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

    Following the fix from PETALSESBCONT-330, some bug appeared in the CDK.

    If a sendAsync expires, then the exchange that was kept is not owned anymore (because it was sent) by the component: thus, the exchange can't ever be queried for information (except for exchangeId and status).

    Currently, exceptions are sometimes thrown in case of expiration.

    Show
    Following the fix from PETALSESBCONT-330, some bug appeared in the CDK. If a sendAsync expires, then the exchange that was kept is not owned anymore (because it was sent) by the component: thus, the exchange can't ever be queried for information (except for exchangeId and status). Currently, exceptions are sometimes thrown in case of expiration.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Victor NOËL made changes - Tue, 8 Sep 2015 - 17:14:28 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Tue, 8 Sep 2015 - 17:14:30 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Victor NOËL added a comment - Tue, 8 Sep 2015 - 17:16:37 +0200

It's fixed for now, but it's not totally clear how to properly handle this kind of situation: maybe the component has the need for accessing these informations...

Maybe send async should be handled by the container instead of the CDK as discussed offline.

Show
Victor NOËL added a comment - Tue, 8 Sep 2015 - 17:16:37 +0200 It's fixed for now, but it's not totally clear how to properly handle this kind of situation: maybe the component has the need for accessing these informations... Maybe send async should be handled by the container instead of the CDK as discussed offline.
Victor NOËL made changes - Tue, 8 Sep 2015 - 17:16:37 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.5.0 [ 10406 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
5h 51m
1
Victor NOËL
Tue, 8 Sep 2015 - 17:14:28 +0200
Open Open In Progress In Progress
2s
1
Victor NOËL
Tue, 8 Sep 2015 - 17:14:30 +0200
In Progress In Progress Resolved Resolved
2m 7s
1
Victor NOËL
Tue, 8 Sep 2015 - 17:16:37 +0200



People

Dates

  • Created:
    Tue, 8 Sep 2015 - 11:23:11 +0200
    Updated:
    Tue, 8 Sep 2015 - 17:16:37 +0200
    Resolved:
    Tue, 8 Sep 2015 - 17:16:37 +0200
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.