-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[UNDERTOW-2241][UNDERTOW-2247][UNDERTOW-2248] Handle write timeout properly so no chunk errors occur #1449
Conversation
3c32a4a
to
03b4de4
Compare
This failed Windows CI. I'll have to do an investigation of the reason for the failure. |
3a2b7fe
to
c4cd8da
Compare
Everything indicates the failure in the fix UNDERTOW-2247 is not fully correct. The failure in Windows is a race condition and it requires further work. I'll get back to this after my PTO, on May. |
I'm closing for now. Will reopen when I get back to it. |
Signed-off-by: Flavia Rainone <frainone@redhat.com>
…and clear the allocated buffer to prevent NPEs when ClosedChannelExceptions and broken pipe SocketExceptions occur. Those NPEs can occur at the points where the buffer is closed and it is already null because the buffer was cleared by an inner recursive call as an attempt to deal with the exception. The broken pipe can occur when a browser tab is closed during the response writing process. Signed-off-by: Flavia Rainone <frainone@redhat.com>
…reset expireTime to -1, disabling future checks for write timeout at timeoutCommand runnable Signed-off-by: Flavia Rainone <frainone@redhat.com>
…ore closing the connection to give a chance to outer channels wrap up. At ChunkedStreamSinkConduit create the last chunk and attempt to flush before truncating writes. Signed-off-by: Flavia Rainone <frainone@redhat.com>
164b176
to
d6d724a
Compare
…ring and, instead, just fail the test if there is no header Signed-off-by: Flavia Rainone <frainone@redhat.com>
…s failed on unrelated PR CIs we know it is a preexisting intermitent failure Signed-off-by: Flavia Rainone <frainone@redhat.com>
d6d724a
to
177dd0e
Compare
Something odd happened wiht this PR that, even after 10 minutes of having pushed my branch, the PR was not updated, but I could see the branch was updated by following the link from the PR page to the branch. |
The new PR is #1489 |
I had to recreate a new PR for the same reason :-( |
Jiras:
https://issues.redhat.com/browse/UNDERTOW-2241
https://issues.redhat.com/browse/UNDERTOW-2247
https://issues.redhat.com/browse/UNDERTOW-2248
2.2.x backport PR: #1450