Petals ESB Container

The Remote Transporter should allow for retry on failure

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 5.0.1
Fix Version/s: None
Component/s: Transporter
Security Level: Public

Description:

Hide

Currently, if an error happens upon delivery on the receiver side of the Remote Transporter, the exchange is sent back in error (see ~~PETALSESBCONT-367~~).

The behaviour of the local transporter is a bit different because upon errors, there is a retry of the router on the sender side.

It would be better if the remote transporter behaved in the same way.

Show
Currently, if an error happens upon delivery on the receiver side of the Remote Transporter, the exchange is sent back in error (see ~~PETALSESBCONT-367~~). The behaviour of the local transporter is a bit different because upon errors, there is a retry of the router on the sender side. It would be better if the remote transporter behaved in the same way.

Environment:

-

Issue Links

Depends

This issue depends on:
PETALSESBCONT-437 Reimplement the Remote TCP transporter with Apache Netty
~~PETALSESBCONT-367~~ The NIO Transporter does not send back exception if an error happens while delivering the message on the receiving side

Activity

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Wed, 14 Sep 2016 - 10:13:14 +0200

Updated:

Wed, 14 Sep 2016 - 10:20:11 +0200