Replies: 2 comments
-
/cc @alesj (grpc), @cescoffier (grpc) |
Beta Was this translation helpful? Give feedback.
0 replies
-
I just found the problem. The problem was a blocking call that was executed in an upper layer of this call. It seems that this blocked each other. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am currently facing a weird problem: I have a gRPC API that I want to call in a Quarkus project. The call is quite simple and just returns a ConfigurationResponse object. When this line is run, I get the TimeoutException from Mutiny, but right after that TimeoutException, the call is executed on the gRPC server. I already tried to run it with .runSubscriptionOn(Infrastructure.getDefaultExecutor()), but that didn't help, too.
Here is the line on how I execute the call:
The grpc client is inject via the constructor of the class.
Any ideas what I am doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions