janwesterkamp commented on issue #6856: URL: https://github.com/apache/camel-quarkus/issues/6856#issuecomment-2527742094
@jamesnetherton, from my higer level view, it looks like the Camel Quarkus `camel-quarkus-rest `usage defaults to use a reactive version/configuration of RESTEasy and adding `camel-quarkus-platform-http` has not effect at all. When doing REST client calls via `camel-quarkus-http` resources get blocked, which results in test failures when the thread limit is reached. When doing REST client calls via `camel-quarkus-vertx-http` resources get blocked too, but they are handeled in some way including writing warings into the log. Blocking could result from long runing IO fetcheing the source data and/or with the JNI. Here is the result - [GDAL](https://gdal.org/en/stable/) is the processing library getting called via JNI and there the warning exceptions starts: ``` 2024-12-09 13:01:57,577 WARN [io.ver.cor.imp.BlockedThreadChecker] (vertx-blocked-thread-checker) Thread Thread[vert.x-eventloop-thread-2,5,main] has been blocked for 2622 ms, time limit is 2000 ms: io.vertx.core.VertxException: Thread blocked at org.gdal.gdal.gdalJNI.AllRegister(Native Method) at org.gdal.gdal.gdal.AllRegister(gdal.java:684) at eu.sensoraktor.platform.service.data.processing.CiUtmJp2ToWgs84.process(CiUtmJp2ToWgs84.java:31) at eu.sensoraktor.platform.service.data.processing.Routes$29.process(Routes.java:2566) at org.apache.camel.support.processor.DelegateSyncProcessor.process(DelegateSyncProcessor.java:65) at org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:808) at org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:714) at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.doRun(DefaultReactiveExecutor.java:199) at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeReactiveWork(DefaultReactiveExecutor.java:189) at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.tryExecuteReactiveWork(DefaultReactiveExecutor.java:166) at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:148) at org.apache.camel.impl.engine.DefaultReactiveExecutor.schedule(DefaultReactiveExecutor.java:54) at org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.lambda$doRun$1(RedeliveryErrorHandler.java:813) at org.apache.camel.component.vertx.http.VertxHttpProducer.lambda$createResultHandler$1(VertxHttpProducer.java:132) at io.vertx.ext.web.client.impl.HttpContext.handleDispatchResponse(HttpContext.java:402) at io.vertx.ext.web.client.impl.HttpContext.execute(HttpContext.java:384) at io.vertx.ext.web.client.impl.HttpContext.next(HttpContext.java:362) at io.vertx.ext.web.client.impl.HttpContext.fire(HttpContext.java:329) at io.vertx.ext.web.client.impl.HttpContext.dispatchResponse(HttpContext.java:291) at io.vertx.ext.web.client.impl.HttpContext.lambda$null$7(HttpContext.java:512) at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:270) at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:252) at io.vertx.core.impl.ContextInternal.lambda$runOnContext$0(ContextInternal.java:50) at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:1583) ``` It also looks like the configuration is ignored - it says 2000ms instead of 1s configured... -- 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
