Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Address
maxConcurrentStreams
violation on write timeout #3908Address
maxConcurrentStreams
violation on write timeout #3908Changes from all commits
225a684
31f6571
e5d769f
fb719ef
df43379
fbd4e8a
8018da1
d1183d8
7d207f9
dca247c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The request doesn't seem to be closed unlike what the method name says?
I maybe miss something, but if the
MAX_CONNECTION_AGE
is two seconds and the response is sent after 4 seconds, shouldn't the connection should be closed forcefully? 馃There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about the late check
Maybe I'm misunderstanding the specification, but I thought that even if
MAX_CONNECTION_AGE
is reached, the client waits for requests to finish (so it doesn't forcefully fail long-running requests). I've updated the test name to better reflect this 馃槄I've also organized how I think
MAX_CONNECTION_AGE
worksA timer is scheduled for
MAX_CONNECTION_AGE
, but is only respected if there are no running requestsarmeria/core/src/main/java/com/linecorp/armeria/internal/common/AbstractKeepAliveHandler.java
Lines 436 to 440 in b77bfbb
Instead, every time a request may have finished, we check if
MAX_CONNECTION_AGE
has passed, and there are no running requests.armeria/core/src/main/java/com/linecorp/armeria/client/Http2ResponseDecoder.java
Lines 153 to 155 in b77bfbb
armeria/core/src/main/java/com/linecorp/armeria/client/Http2ResponseDecoder.java
Lines 215 to 217 in b77bfbb
armeria/core/src/main/java/com/linecorp/armeria/client/Http2ResponseDecoder.java
Lines 275 to 279 in b77bfbb
MAX_CONNECTION_AGE
has passed.armeria/core/src/main/java/com/linecorp/armeria/client/HttpSessionHandler.java
Line 163 in b77bfbb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for that. 馃槃
Exactly. My memory was wrong. Thanks for checking it. 馃槃