-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
gRPC connection fails #24305
Labels
Comments
@garethj2, thanks for opening the issue! I appreciate if you can provide a reproducible. It will fast track the process to fix the bug. |
As requested, I've created a reproducible test case that reproduces the issue... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: Deno 1.44.4
Client
@grpc/grpc-js: 1.10.9
@grpc/grpc-proto-loader: 0.7.13
Server
C++ gRPC version 1.51.1#3
I've been testing out the client of
@grpc/grpc-js
with Deno. In my code, I create a stream and listen for some events. After a period of time, I don't receive any more events and no morerpc
calls seem to work.Please note, I've run the exact same code using NodeJS and there appears to be no problem.
I've enabled logging in
@grpc/grpc-js
to help diagnose the issue. Here's a code snippet from@grpc/grpc-js
where everything stops. Please see here for more details...When everything stops working, the last trace I get is from
receive HTTP/2 data frame of length
. Thepassed message of length
line is never reached.Please note, I don't get any other errors. I have been monitoring the connection state using the recommended callbacks and I get nothing. It's almost like something goes fundamentally wrong with either the HTTP/2 connection or the Buffer being used to hold any received data.
Interestingly, the more events I ask for in my data stream, the quicker this problem occurs. With my default set up (i.e. 8 events), it takes about 100 seconds for the problem to occur. Here's an example of the type of data I receive in a response when everything does work...
I've tried changing some of the default buffer sizes when opening the client connection. Nothing seems to make any difference. BTW when I set a keep alive message, I get a completely different broken pipe error but that's a completely different issue.
Hopefully this is enough information to track down whatever the issue may be.
The text was updated successfully, but these errors were encountered: