[
https://issues.apache.org/jira/browse/CAMEL-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522161#comment-17522161
]
Nicolas Filotto commented on CAMEL-17948:
-----------------------------------------
One test is failing due to this change which is {{
org.apache.camel.component.ahc.ws.WsProducerConsumerTest.testRestartServer}}
more details here
https://ci-builds.apache.org/job/Camel/job/Apache%20Camel/job/main/247/testReport/
> Race condition in MockEndpoint with PER_CLASS tests
> ---------------------------------------------------
>
> Key: CAMEL-17948
> URL: https://issues.apache.org/jira/browse/CAMEL-17948
> Project: Camel
> Issue Type: Bug
> Components: camel-mock
> Affects Versions: 3.16.0
> Reporter: Nicolas Filotto
> Assignee: Nicolas Filotto
> Priority: Major
> Fix For: 3.17.0
>
>
> While working on CAMEL-17945, I realized that the tests with the scope
> {{PER_CLASS}} leveraging the {{MockEndpoint}} to define their assertions can
> fail randomly because of a race condition issue. Indeed, with the current
> code, a message of a previous test method can potentially call the method
> {{countDown}} on the latch of the following test method causing unexpected
> behavior.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
