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
-
- Environment:
- -
Issue Links
| Depends | ||||
|---|---|---|---|---|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Link |
This issue depends on |
| Description |
Currently, if an error happens upon delivery on the receiver side of the Remote Transporter, the exchange is sent back in error.
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. |
Currently, if an error happens upon delivery on the receiver side of the Remote Transporter, the exchange is sent back in error (see 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. |
| Link | This issue depends on PETALSESBCONT-437 [ PETALSESBCONT-437 ] |