camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Resequencer inout support
Date Thu, 01 Oct 2015 11:44:33 GMT

Yeah that is not possible. The resequencer works like the aggregator.
The incoming message is accepted by the eip, and then that message
continue routing.

The this eip is stateful and based on some worker tasks it output new
messages when it should, such as for  the resequencer when the
messages are in order, and for the aggregateor, when a group is
complete etc.

On Wed, Sep 30, 2015 at 10:14 PM, prasadrao82 <> wrote:
> Hi All,
> Greetings for the day!!, We are working on following requirement on Q
> priority , where we receive online request(synchronous) from multiple
> customers, We need to resequence the message based on the customer and
> respond.
> We tried with resequncer , its working with resequencing the priority, but
> unable to give control back to the camel , which invoked this resequencer.
> Seems resequencer is supporting only with IN pattern. If this the case , the
> control return to caller is not happening , with that customer who invoke
> the application , will not get the response. even though it processed.
> Could someone help us on this.
> And also support us , whether camel has any other best approach for this
> requirment
> Thanks in advance.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
----------------- @davsclaus
Camel in Action 2nd edition:

View raw message