骆驼组播异常传播

时间:2016-03-09 15:51:40

标签: apache-camel

当Camel被抛出多播时,它不会传播异常。

给出以下设置,其中direct:route从其beanRef:

中抛出异常
        rest("/...")
        .post()
        .consumes("application/json")
        .produces("application/json")
        .route()
            .onException(Exception.class)
                .handled(true)
                .bean("exceptionHandler")
                .marshal("exceptionDataFormat")
            .end()
            .unmarshal("dataFormat")
            ...
            .enrich("direct:services", new ServiceAggregator())
            .to("direct:anotherRoute")
            ...
        .end()
    .endRest();


    from("direct:services")
        .errorHandler(noErrorHandler())
        .multicast()
        .setAggregationStrategy(new GroupedExchangeAggregationStrategy())
        .executorServiceRef("executor")
        .parallelAggregate()
        .streaming()
        .stopOnException()
            .to("direct:route")
        .end()
    .end();

    from("direct:route")
        .errorHandler(noErrorHandler())
        .bean("someRef", "someMethod")
    .end();

不是允许异常处理程序使用交换并处理错误,而是立即返回以下异常(到SoapUI):

org.apache.camel.CamelExchangeException: Parallel processing failed for number 0. Exchange[...] at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:328)
at org.apache.camel.processor.MulticastProcessor$1.call(MulticastProcessor.java:299)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

并且父路由以该异常结束并且没有异常处理。

如果direct:anotherRoute抛出异常,则会正确处理该异常。

为什么我不能将多播异常传播到父路由?

Camel 2.17-SNAPSHOT

2 个答案:

答案 0 :(得分:5)

打开多播上的shareUnitOfWork选项。有关详细信息,请参阅:http://camel.apache.org/multicast并且分割器上有一个示例,它也有此选项:http://camel.apache.org/splitter.html

答案 1 :(得分:0)

尝试使用

.errorHandler(noErrorHandler()) 

在父路由和子路由中将异常传播到 onexception()