Petals SE Camel

Mixup with Exchange Properties between Petals Consumers and Providers

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.5.0
  • Fix Version/s: 0.5.1, 0.5.2, 1.0.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When a Petals exchange arrives on the Camel SE, its properties (not the message properties, that are business-specific but the exchange's) are copied to the Camel exchange.
    When a Camel exchange is sent to Petals, its properties (exchange's again) are copied to the newly sent Petals Exchange.

    There is thus a mixup with Flow Attributes, or CDK async property, etc.

    It is not possible to simply not forward them, because we actually don't know if some properties are not added explicitly by the route (for Camel exchanges sent to Petals), or if the properties set by another Petals service is needed in the route (for Petals exchanges sent received by Camel).

    It is not yet clear how to fix this.

    Show
    When a Petals exchange arrives on the Camel SE, its properties (not the message properties, that are business-specific but the exchange's) are copied to the Camel exchange. When a Camel exchange is sent to Petals, its properties (exchange's again) are copied to the newly sent Petals Exchange. There is thus a mixup with Flow Attributes, or CDK async property, etc. It is not possible to simply not forward them, because we actually don't know if some properties are not added explicitly by the route (for Camel exchanges sent to Petals), or if the properties set by another Petals service is needed in the route (for Petals exchanges sent received by Camel). It is not yet clear how to fix this.
  • Environment:
    -

Activity

Hide
Victor NOËL added a comment - Fri, 11 Sep 2015 - 09:33:37 +0200

For now, we do not transfer properties, see https://github.com/petalslink/petals-se-camel/commit/1e3436960eb28f9990f69aae84044aacbc242739

But we should find a better solution...

Show
Victor NOËL added a comment - Fri, 11 Sep 2015 - 09:33:37 +0200 For now, we do not transfer properties, see https://github.com/petalslink/petals-se-camel/commit/1e3436960eb28f9990f69aae84044aacbc242739 But we should find a better solution...
Hide
Victor NOËL added a comment - Fri, 11 Sep 2015 - 10:03:13 +0200
Show
Victor NOËL added a comment - Fri, 11 Sep 2015 - 10:03:13 +0200 This temporary fix was backported for Petals 4.3.x (see https://github.com/petalslink/petals-se-camel/commit/fb181b9db3c04d39001c20b3cd8d371a76e11c70)
Hide
Victor NOËL added a comment - Thu, 1 Oct 2015 - 09:29:53 +0200

A preliminary fix is in v0.5.1 (and thus will be in 1.0.0 at least).

Show
Victor NOËL added a comment - Thu, 1 Oct 2015 - 09:29:53 +0200 A preliminary fix is in v0.5.1 (and thus will be in 1.0.0 at least).
Hide
Victor NOËL added a comment - Thu, 1 Oct 2015 - 09:30:28 +0200

Reopening because there is more work to do.

Show
Victor NOËL added a comment - Thu, 1 Oct 2015 - 09:30:28 +0200 Reopening because there is more work to do.
Hide
Victor NOËL added a comment - Mon, 12 Sep 2016 - 11:04:34 +0200 - edited
Show
Victor NOËL added a comment - Mon, 12 Sep 2016 - 11:04:34 +0200 - edited This was actually fixed with PETALSSECAMEL-16, PETALSSECAMEL-17, PETALSSECAMEL-22 and PETALSDISTRIB-282

People

Dates

  • Created:
    Fri, 11 Sep 2015 - 09:32:06 +0200
    Updated:
    Mon, 12 Sep 2016 - 11:05:08 +0200
    Resolved:
    Mon, 12 Sep 2016 - 11:04:34 +0200