Petals ESB Container

A sendSync should be blocked at router level instead of transporter level

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

Details

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

Description:

Hide

When a message exchange is sent synchronously, the sending is blocked at transporter level to wait the result (reply or ack).
If the message exchange is sent asynchronously, the emitter will wait the result at router level.

So, it is more consistent to block in the same place for synchronous and asynchronous invocations, at router level.

Show
When a message exchange is sent synchronously, the sending is blocked at transporter level to wait the result (reply or ack). If the message exchange is sent asynchronously, the emitter will wait the result at router level. So, it is more consistent to block in the same place for synchronous and asynchronous invocations, at router level.

Environment:

-

Issue Links

Depends

This issue blocks:
~~PETALSESBCONT-364~~ "No endpoint(s) matching the target service" when attaching a container

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

3d 1h 56m

1

Victor NOËL

Mon, 30 Nov 2015 - 12:09:15 +0100

Open

In Progress

3s

1

Victor NOËL

Mon, 30 Nov 2015 - 12:09:18 +0100

In Progress

Resolved

22h 6m

1

Victor NOËL

Tue, 1 Dec 2015 - 10:16:16 +0100

People

Assignee:

Victor NOËL

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Fri, 27 Nov 2015 - 10:12:29 +0100

Updated:

Tue, 1 Dec 2015 - 10:16:16 +0100

Resolved:

Tue, 1 Dec 2015 - 10:16:15 +0100