llowinge commented on issue #7897:
URL: https://github.com/apache/camel-quarkus/issues/7897#issuecomment-3479467517
Thank you @apupier . This is the relevant log:
```
2025-10-24 14:27:58,462 INFO [org.apa.cam.qua.com.grp.it.GrpcTest] (main)
Running test method: forwardOnError()
2025-10-24 14:27:58,463 INFO [org.apa.cam.qua.com.grp.it.GrpcTest] (main)
forwardOnError: preparing observers
2025-10-24 14:27:58,463 INFO [org.apa.cam.qua.com.grp.it.GrpcTest] (main)
forwardOnError: calling onNext(null)
2025-10-24 14:27:58,463 INFO [org.apa.cam.qua.com.grp.it.GrpcTest] (main)
forwardOnError: waiting latch.await(5s)
2025-10-24 14:27:58,473 INFO [org.apa.cam.qua.com.grp.it.GrpcTest]
(grpc-default-executor-0) PongResponseStreamObserver#onNext:
Error: Exception in thread "grpc-default-executor-0"
java.lang.IllegalStateException: Forced exception
at
org.apache.camel.quarkus.component.grpc.it.GrpcTest$PongResponseStreamObserver.onNext(GrpcTest.java:686)
at
org.apache.camel.quarkus.component.grpc.it.GrpcTest$PongResponseStreamObserver.onNext(GrpcTest.java:658)
at
io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onMessage(ClientCalls.java:568)
at
io.grpc.internal.DelayedClientCall$DelayedListener$2.run(DelayedClientCall.java:476)
at
io.grpc.internal.DelayedClientCall$DelayedListener.drainPendingCallbacks(DelayedClientCall.java:526)
at
io.grpc.internal.DelayedClientCall$1DrainListenerRunnable.runInContext(DelayedClientCall.java:315)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at java.base/java.lang.Thread.run(Thread.java:1474)
2025-10-24 14:28:03,466 INFO [org.apa.cam.qua.com.grp.it.GrpcTest] (main)
Finished test forwardOnError
```
Basically the method `onError` wasn't called in 5s timeout after the
simulated exception was thrown in `onNext`. Which is weird, as it should be
high enough number. I would for now leave it as it is and we will see if it
happens in future. We could be just really unlucky with some atypical slowness
of the CI machine.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
