JiriOndrusek commented on PR #3919: URL: https://github.com/apache/camel-quarkus/pull/3919#issuecomment-1197781365
I still don't know why, but `ordering test`, as was created in the beginning, fails in CLI. The original test was sending **6** messages and receives them afterwards. In CLI there was a failure (without any obvious reason) with the 3rd message. Here is a log snippet: ``` 022-07-27T13:37:14.9565463Z 2022-07-27 13:37:14,950 DEBUG [org.apa.cam.com.goo.pub.GooglePubsubProducer] (executor-thread-0) uploader thread/id: 126 / 64C35E7D9B618FD-0000000000000008. api call completed. 2022-07-27T13:37:14.9565962Z 2022-07-27 13:37:14,950 TRACE [org.apa.cam.pro.err.RedeliveryErrorHandler] (executor-thread-0) This exchange is not handled or continued so its marked as failed: Exchange[64C35E7D9B618FD-0000000000000008] 2022-07-27T13:37:14.9566895Z 2022-07-27 13:37:14,953 ERROR [org.apa.cam.pro.err.DefaultErrorHandler] (executor-thread-0) Failed delivery for (MessageId: 64C35E7D9B618FD-0000000000000008 on ExchangeId: 64C35E7D9B618FD-0000000000000008). Exhausted after delivery attempt: 1 caught: java.util.concurrent.ExecutionException: java.util.concurrent.CancellationException: Execution cancelled because executing previous runnable failed. ``` Ordering test in Camel Quarkus does not need to test functionality, but it should cover that CQ extension works with the requested configuration. In my POV it is enough to see that **2** messages are delivered during ordering test, because we can state, that it is possible to call ordering capability of the extension. Ordering itself is "executed" by the google pubsub provider. I reported this "unknown" failure for further investigation as a [ticket](https://github.com/apache/camel-quarkus/issues/3944) I think that this PR could be merged and the ordering test is covering the ordering feature even with this stripped scenario. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
