On Thu, Aug 5, 2010 at 1:07 PM, Marco Crivellaro
<marco.crivell...@optasports.com> wrote:
>
> I am using 2.5-SNAPSHOT I've updated my local repo this morning
>
> timeout seems to have a problem even on your Unit test route:
>
> from("direct:start")
> .recipientList(header("slip")).aggregationStrategy(
> new AggregationStrategy() {
> public Exchange aggregate(Exchange oldExchange,
> Exchange newExchange) {
> if (oldExchange == null) {
> return newExchange;
> }
>
> String body =
> oldExchange.getIn().getBody(String.class);
> oldExchange.getIn().setBody(body +
> newExchange.getIn().getBody(String.class));
> return oldExchange;
> }
> })
> .parallelProcessing().timeout(2000)
> .to("mock:result");
>
The unit test works perfect. It has been tested by an army of
different servers in the CI farm.
Could be some weird on your end. Try compile from a cmd line or
something. And ensure you dont have old jars in the classpath.
And what error do you get?
>
>
> it looks fine on multicast route:
> from("direct:start")
> .multicast(new AggregationStrategy() {
> public Exchange aggregate(Exchange
> oldExchange, Exchange
> newExchange) {
> if (oldExchange == null) {
> return newExchange;
> }
>
> String body =
> oldExchange.getIn().getBody(String.class);
> oldExchange.getIn().setBody(body +
> newExchange.getIn().getBody(String.class));
> return oldExchange;
> }
> })
>
> .parallelProcessing().timeout(2000).to("direct:a", "direct:b",
> "direct:c")
> // use end to indicate end of multicast route
> .end()
> .to("mock:result");
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-2-5-recipientList-aggregationStrategy-timeout-tp2265144p2265166.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
