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

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.