Petals ESB Container

Do not remove In, Out or Fault from an Exchange before sending it

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.3.0
  • Fix Version/s: 5.0.0
  • Component/s: Router, Transporter
  • Security Level: Public
  • Description:
    Hide

    Before sending an exchange, the router "cleans" its messages to remove those that were already here before, for example if it's a DONE or ERROR status, all message are removed, or if it's an OUT, the IN message is removed.
    There is more strange and not always coherent logic to it.

    We shouldn't do that, I guess the objective is to save bandwidth when transferring over the network, but removing these messages kind of breaks the JBI specs, and makes checking the for state error very difficult (as in PETALSESBCONT-74).

    The alternative is to simply have more "intelligent" transporters (for now only the NIO transporter) so that it only transfers what should be transferred.

    Show
    Before sending an exchange, the router "cleans" its messages to remove those that were already here before, for example if it's a DONE or ERROR status, all message are removed, or if it's an OUT, the IN message is removed. There is more strange and not always coherent logic to it. We shouldn't do that, I guess the objective is to save bandwidth when transferring over the network, but removing these messages kind of breaks the JBI specs, and makes checking the for state error very difficult (as in PETALSESBCONT-74). The alternative is to simply have more "intelligent" transporters (for now only the NIO transporter) so that it only transfers what should be transferred.
  • Environment:
    -

Issue Links

Activity

People

Dates

  • Created:
    Wed, 15 Jul 2015 - 16:30:35 +0200
    Updated:
    Tue, 21 Jul 2015 - 17:17:38 +0200
    Resolved:
    Tue, 21 Jul 2015 - 17:17:37 +0200