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

intermittent h2 timing test failure #11785

Closed
loriadi opened this issue Apr 16, 2020 · 0 comments · Fixed by #11787
Closed

intermittent h2 timing test failure #11785

loriadi opened this issue Apr 16, 2020 · 0 comments · Fixed by #11787
Assignees
Labels
in:Transport release bug This bug is present in a released version of Open Liberty release:20005 team:Sirius

Comments

@loriadi
Copy link
Contributor

loriadi commented Apr 16, 2020

The request is sent by the client with the http/2 upgrade header h2c.
The server accepts the upgrade and replies with the 101 response.
The connection preface is sent by the client with an empty settings frame, all good so far.
The server has stored away the initial request, waiting for the connection to complete setup.
The connection is completed, the server starts to process the initial request.
The server is interrupted, and another settings frame comes in, this one has a bad size.
The server processes this frame, sees the error, sends a goaway frame, and cleans up everything - streams, links, etc.

The server then returns to process the initial servlet request, but all the resources for the request were released, and then it gets the NPE, The actual NPE occurs on when the servlet tries to get the response, and it's null.

@loriadi loriadi self-assigned this Apr 16, 2020
@loriadi loriadi added in:Transport release bug This bug is present in a released version of Open Liberty team:Sirius labels Apr 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in:Transport release bug This bug is present in a released version of Open Liberty release:20005 team:Sirius
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants