Petals ESB Container

The NIO Transporter does not send back exception if an error happens while delivering the message on the receiving side

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.0
  • Fix Version/s: 5.0.1
  • Component/s: Transporter
  • Security Level: Public
  • Description:
    Hide

    To improve reliability, it would be better if the NIO transporter would send back to the sender the error that happened on the receiving side (for example a component queue without space) so that the sender can try other endpoints if there is some.

    This is part of the effort to improve reliability in Petals: PETALSDISTRIB-146

    Show
    To improve reliability, it would be better if the NIO transporter would send back to the sender the error that happened on the receiving side (for example a component queue without space) so that the sender can try other endpoints if there is some. This is part of the effort to improve reliability in Petals: PETALSDISTRIB-146
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Victor NOËL added a comment - Mon, 11 Jan 2016 - 15:02:43 +0100

Fixed in trunk, the error is sent back as an exchange through the router and not as a thrown exception because the NIO transporter is not built to send back an exception.

It is not really a problem, but it means the behaviour is a bit different than in local mode.
The main idea is that catching an exception from a send or receiving back an error in the exchange from a send should be considered equivalent for the sender.

Show
Victor NOËL added a comment - Mon, 11 Jan 2016 - 15:02:43 +0100 Fixed in trunk, the error is sent back as an exchange through the router and not as a thrown exception because the NIO transporter is not built to send back an exception. It is not really a problem, but it means the behaviour is a bit different than in local mode. The main idea is that catching an exception from a send or receiving back an error in the exchange from a send should be considered equivalent for the sender.
Hide
Permalink
Victor NOËL added a comment - Tue, 12 Jan 2016 - 10:40:39 +0100

Reopen: it is not totally acceptable to send back an error, it would be best that an exception is sent back to the sender node so that its router can re-route the exchange like it does when a local delivery fails.

Show
Victor NOËL added a comment - Tue, 12 Jan 2016 - 10:40:39 +0100 Reopen: it is not totally acceptable to send back an error, it would be best that an exception is sent back to the sender node so that its router can re-route the exchange like it does when a local delivery fails.
Hide
Permalink
Victor NOËL added a comment - Wed, 14 Sep 2016 - 10:15:30 +0200

The extra requirements that the remote transporter should allow for retry to happen on the sender side has been moved to PETALSESBCONT-438.

Show
Victor NOËL added a comment - Wed, 14 Sep 2016 - 10:15:30 +0200 The extra requirements that the remote transporter should allow for retry to happen on the sender side has been moved to PETALSESBCONT-438.

People

Dates

  • Created:
    Fri, 27 Nov 2015 - 09:53:06 +0100
    Updated:
    Wed, 14 Sep 2016 - 10:15:30 +0200
    Resolved:
    Wed, 14 Sep 2016 - 10:15:30 +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.