Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of sdahl@carefx.com designates
 208.93.129.136 as permitted sender)
From: Sandi Dahl <sdahl@carefx.com>
To: "dev@camel.apache.org" <dev@camel.apache.org>
Date: Tue, 26 Apr 2011 10:44:46 -0700
Subject: RE: recipient list and timeouts
Thread-Topic: recipient list and timeouts
Thread-Index: AcwEOB+zD3aeU/dhTvS7gDDqSvOQxAAAJHEw
Message-ID: <70171946FE74F54599A5FAC47922AE6305E391C7AC@mailstore>
References: <70171946FE74F54599A5FAC47922AE6305E391C7AA@mailstore>
 <BANLkTinSw7=B-ttr_yunCLcP7O3z99xF3A@mail.gmail.com>
In-Reply-To: <BANLkTinSw7=B-ttr_yunCLcP7O3z99xF3A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks! Sorry for using the wrong list.

-----Original Message-----
From: Claus Ibsen [mailto:claus.ibsen@gmail.com]=20
Sent: Tuesday, April 26, 2011 10:33 AM
To: dev@camel.apache.org
Subject: Re: recipient list and timeouts

On Tue, Apr 26, 2011 at 7:23 PM, Sandi Dahl <sdahl@carefx.com> wrote:
> I am a new developer working with Camel. We need to route messages using =
a parallel processed recipient list. We are using an aggregation strategy t=
o combine the results into one message.
>
> Our requirements include the need to know which specific endpoints did no=
t respond before a time out occurs. We need this information to display to =
the user so they understand what information is included in the results. I =
understand a TimeoutAwareAggregationStrategy can be used which will call ti=
meout() before ending.
>
> Is it possible to discover which specific endpoints did not respond withi=
n the specified timeout period rather than just knowing that all did not co=
mplete in time?

You need to bookkeep that yourself. For example in the aggregate
method. If its invoked you know that endpoint returned back a
response.

On the Exchange there is a header (or property on exchange) with a
Exchange.TO_ENDPOINT key that ought to have the uri of the endpoint
where the recipient list send it.

Oh and you should use the @user mailinglist for questions about using Camel=
.


>
> Thanks!
> Sandi
>
>
>


--=20
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/