-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.InvalidOperationException: The pipe is in a disconnected state! #62
Comments
I have not encoutered this issue in 2.1. After updating to 3.0, it occured once time. I will go with more test. |
I suspect that it is related to this commit |
We are getting the same exception. Do you happen to have any updates on this? |
This exception occurred only in the virtual machine environment. When tested on physical hardware, the program ran continuously for over 5 days without any issues. While there are several differences between these two environments beyond the virtual/physical distinction, this issue has never been reported in any customer environment. Given these observations, I believe this exception is environment-specific. |
There was a communication error during more than 20,000 Unary requests being executed.
the server's error is as follows: caught by NamedPipeServer.Error event.
System.InvalidOperationException: The pipe is in a disconnected state!
and the client error is:
Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="failed to connect to all addresses")
在 System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
在 System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
在 GrpcDotNetNamedPipes.Internal.MessageReader`1.d__5.MoveNext()
After this error, everything was going well.
The text was updated successfully, but these errors were encountered: