You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Nicolas Filotto (Jira)" <ji...@apache.org> on 2022/10/24 08:49:00 UTC
[jira] [Resolved] (CAMEL-18633) Wrong debug log output when using MockEndpoint
[ https://issues.apache.org/jira/browse/CAMEL-18633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Filotto resolved CAMEL-18633.
-------------------------------------
Assignee: Nicolas Filotto
Resolution: Fixed
Thanks for reporting.
Fixed by https://github.com/apache/camel/commit/6dda0f98add093b87daa9fa9557bbfa936876b43
> Wrong debug log output when using MockEndpoint
> ----------------------------------------------
>
> Key: CAMEL-18633
> URL: https://issues.apache.org/jira/browse/CAMEL-18633
> Project: Camel
> Issue Type: Task
> Components: camel-test
> Reporter: Manuel Langer
> Assignee: Nicolas Filotto
> Priority: Minor
> Fix For: 3.20.0
>
>
> In class org.apache.camel.component.mock.MockEndPoint, there is bug in the following method:
> protected void waitForCompleteLatch(long timeout) throws InterruptedException {
> // Wait for a default 10 seconds if resultWaitTime is not set
> long waitTime = timeout == 0 ? 10000L ** : timeout{*};{*}
> // now let's wait for the results
> {_}LOG{_}.debug("Waiting on the latch for: {} millis"{*},{*} {color:#ff0000}*timeout*{color}){*};{*}
> ** if (!latch.await(waitTime, TimeUnit.{_}MILLISECONDS{_})) {
> {_}LOG{_}.warn("The latch did not reach 0 within the specified time"){*};{*}
> }
> }
> Use waitTime instead of timeout in the debug log:
> {_}LOG{_}.debug("Waiting on the latch for: {} millis"{*},{*} timeout){*};{*}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)