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

Netty error log can be seen when server closes the connection after sending a goaway #6050

Closed
dilanSachi opened this issue Feb 13, 2024 · 0 comments · Fixed by ballerina-platform/module-ballerina-http#1854
Assignees
Labels
Area/http2 module/http Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/PCM Protocol connector packages related issues Type/Bug
Milestone

Comments

@dilanSachi
Copy link
Contributor

Description:
Usually after a server sends a GO_AWAY, it can close the connection. In the current implementation, when the client receives a GO_AWAY, the channel is put into a stale list and a timer task is run to close the stale channels (connections). This is put there as a measure to close the channels when the server does not close the connection. But in a scenario where the server closes the connection, the timer task will also try to close the connection again. This needs to be avoided.

Related internal issue - https://github.com/wso2-enterprise/internal-support-ballerina/issues/588

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/http2 module/http Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/PCM Protocol connector packages related issues Type/Bug
Projects
Archived in project
1 participant