You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a blocking stub to frame a grpc message, I am observing that my GRPC call parks the calling thread indefinitely. I always see a logged exception detailing why the request failed, but the GRPC call does not return.
When using a blocking stub to frame a grpc message, I am observing that my GRPC call parks the calling thread indefinitely. I always see a logged exception detailing why the request failed, but the GRPC call does not return.
I have set up a repro in this repository: https://github.com/jackrwoods/grpc-problem-repro. I've reproduced this behavior with a "blocking" stub (https://github.com/jackrwoods/grpc-problem-repro/blob/main/src/main/java/org/example/Main.java) and a coroutine stub wrapped with a
runBlocking
(https://github.com/jackrwoods/grpc-problem-repro/blob/main/src/main/kotlin/org/example/MainKotlinCoroutineVersion.kt). In both cases, the application never reaches theprintln("Received message")
statement.Is this user (me) error, or is there a workaround?
The text was updated successfully, but these errors were encountered: