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

Correctly buffer multiple outbound streams if needed. #8694

Merged
merged 1 commit into from
Jan 14, 2019

Conversation

normanmaurer
Copy link
Member

Motivation:

In Http2FrameCodec we made the incorrect assumption that we can only have 1 buffered outboundstream as maximum. This is not correct and we need to account for multiple buffered streams.

Modifications:

  • Use a map to allow buffer multiple streams
  • Add unit test.

Result:

Fixes #8692.

@normanmaurer
Copy link
Member Author

Reported by @angn

@normanmaurer
Copy link
Member Author

@netty-bot test this please

Copy link
Contributor

@bryce-anderson bryce-anderson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It took me a few minutes to figure out why this would result in the stack trace in #8692, which I believe is that when we buffer more than one stream we skip setting the stream property but the connection does actually know about the stream. It might be nice to explain that a bit in the commit message. Then again, maybe it's obvious to everyone else.

@normanmaurer
Copy link
Member Author

@bryce-anderson added a comment in the code to explain why a map is needed.

Motivation:

In Http2FrameCodec we made the incorrect assumption that we can only have 1 buffered outboundstream as maximum. This is not correct and we need to account for multiple buffered streams.

Modifications:

- Use a map to allow buffer multiple streams
- Add unit test.

Result:

Fixes #8692.
@normanmaurer normanmaurer merged commit 4155bc0 into 4.1 Jan 14, 2019
@normanmaurer normanmaurer deleted the buffered_stream_fix branch January 14, 2019 07:25
normanmaurer added a commit that referenced this pull request Jan 14, 2019
Motivation:

In Http2FrameCodec we made the incorrect assumption that we can only have 1 buffered outboundstream as maximum. This is not correct and we need to account for multiple buffered streams.

Modifications:

- Use a map to allow buffer multiple streams
- Add unit test.

Result:

Fixes #8692.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants