Petals ESB Container

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

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: 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

Activity

Christophe DENEUX made changes - Fri, 27 Nov 2015 - 10:13:16 +0100
Field Original Value New Value
Link This issue blocks PETALSESBCONT-364 [ PETALSESBCONT-364 ]
Hide
Victor NOËL added a comment - Fri, 27 Nov 2015 - 10:14:18 +0100

I'm currently working on that (as I told you before) and my solution is actually different than this proposition, we should discuss it together.

Show
Victor NOËL added a comment - Fri, 27 Nov 2015 - 10:14:18 +0100 I'm currently working on that (as I told you before) and my solution is actually different than this proposition, we should discuss it together.
Victor NOËL made changes - Mon, 30 Nov 2015 - 12:09:05 +0100
Priority Blocker [ 1 ]
Description 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 through the method {{RouterService.receive}}.

So, it is more consistent to block in the same place for synchronous and asynchronous invocations, at router level.
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.
Victor NOËL made changes - Mon, 30 Nov 2015 - 12:09:15 +0100
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ] Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Mon, 30 Nov 2015 - 12:09:18 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Tue, 1 Dec 2015 - 10:16:16 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 5.0.1 [ 10579 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
3d 1h 56m
1
Victor NOËL
Mon, 30 Nov 2015 - 12:09:15 +0100
Open Open In Progress In Progress
3s
1
Victor NOËL
Mon, 30 Nov 2015 - 12:09:18 +0100
In Progress In Progress Resolved Resolved
22h 6m
1
Victor NOËL
Tue, 1 Dec 2015 - 10:16:16 +0100



People

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