io.grpc.StatusRuntimeException

INTERNAL: Connection closed with unknown cause

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web84

  • via Google Groups by Ivan Vaskevych, 9 months ago
    INTERNAL: Connection closed with unknown cause
  • via GitHub by yashmuni
    , 6 months ago
    INTERNAL: Connection closed with unknown cause
  • UNAVAILABLE: Transport closed for unknown reason
  • Stack trace

    • io.grpc.StatusRuntimeException: INTERNAL: Connection closed with unknown cause at io.grpc.Status.asRuntimeException(Status.java:545) at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:395) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:481) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:398) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:513) at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:52) at io.grpc.internal.SerializingExecutor$TaskRunner.run(SerializingExecutor.java:154) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    22 times, 5 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 2 weeks ago
    19 times, 3 months ago
    Unknown user
    Once, 1 year ago
    2 more bugmates