You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/03 10:37:00 UTC

[jira] [Resolved] (CAMEL-17179) XXXParallelWithAggregationStrategyThrowingExceptionTest often fail

     [ https://issues.apache.org/jira/browse/CAMEL-17179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-17179.
---------------------------------
    Resolution: Fixed

> XXXParallelWithAggregationStrategyThrowingExceptionTest often fail
> ------------------------------------------------------------------
>
>                 Key: CAMEL-17179
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17179
>             Project: Camel
>          Issue Type: Sub-task
>          Components: came-core
>    Affects Versions: 3.13.0
>            Reporter: Karen Lease
>            Priority: Major
>
> The unit tests in package org.apache.camel.issues:
>  - SplitterParallelWithAggregationStrategyThrowingExceptionTest
>  - MulticastParallelWithAggregationStrategyThrowingExceptionTest
>  - RecipientListParallelWithAggregationStrategyThrowingExceptionTest
> often fail even after 3 tries. The tests assume that all threads to send messages have at least been scheduled before aggregate is called for the first time which stops the processing. But under heavy parallel processing, this frequently does not occur, causing the test to fail.
> In fact, the test assumption seems incorrect; there is no guarantee that any multicast destination other than the one triggering the aggregation exception will be reached.
> In addition, while examining the code, I found that the multicast option stopOnAggregateException has no effect. Whether or not it is used, an exception thrown in the aggregation strategy is always causes the processing to stop and the error handler to be triggered. See linked issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)