Skip to content
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

Connection closed by server after 20s vs. keep-alive #996

Open
tomas0svk opened this issue Nov 28, 2023 · 0 comments
Open

Connection closed by server after 20s vs. keep-alive #996

tomas0svk opened this issue Nov 28, 2023 · 0 comments
Labels
question A question about this library or its usage

Comments

@tomas0svk
Copy link

The context

Hello. I am trying to equalize keep-alive settings between client and server to avoid unnecessary go-aways due to misbehaving clients

The question

I came across a strange behavior.
If there is no interaction between client and server, 20s after last HTTP2/RST_STREAM, server sends HTTP2/GOAWAY which leads to closing of HTTP2 as well as TCP connection.
This happens both

  • If there is enable-keep-alive set to false in both client and server (which is expected)
  • If I changed enable-keep-alive and permit-keep-alive-without-calls to true, HTTP2/PINGs are being sent but connection is terminated anyway

Is this expected behavior?
Am I able to change the timeout? Or rather... Am I supposed to change this, or this is a sensible default?
Thank you

Stacktraces and logs

image

The application's environment

  • Spring (boot): 2.7.5
  • grpc-java: 1.59.0
  • grpc-spring-boot-starter: 2.15.0.RELEASE
  • java: version + architecture (64bit?): 11.0.18+10-LTS, Kotlin: 1.9.10
@tomas0svk tomas0svk added the question A question about this library or its usage label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question A question about this library or its usage
Projects
None yet
Development

No branches or pull requests

1 participant