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

[UNDERTOW-2241][UNDERTOW-2247][UNDERTOW-2248] Handle write timeout properly so no chunk errors occur #1450

Closed

Conversation

@fl4via fl4via added bug fix Contains bug fix(es) waiting CI check Ready to be merged but waiting for CI check maintenance branch Targeting maintainance branch and removed bug fix Contains bug fix(es) labels Mar 24, 2023
@fl4via fl4via force-pushed the UNDERTOW-2241_2247_2248_2.2.x branch 4 times, most recently from 24f51ae to 09f3d49 Compare March 24, 2023 03:16
@fl4via fl4via changed the base branch from master to 2.2.x March 24, 2023 03:18
@fl4via fl4via added waiting PR update Awaiting PR update(s) from contributor before merging failed CI Introduced new regession(s) during CI check and removed waiting CI check Ready to be merged but waiting for CI check labels Mar 24, 2023
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>
@fl4via fl4via force-pushed the UNDERTOW-2241_2247_2248_2.2.x branch from 3bd90e1 to 62b575b Compare March 29, 2023 17:54
@fl4via
Copy link
Member Author

fl4via commented Apr 23, 2023

I"m closing for now, this requires further investigation.

@fl4via
Copy link
Member Author

fl4via commented Jun 7, 2023

For the same reasons I had to close #1449 I'll have to close this one and open a new PR: updating the branch with force pushing is not updating the PR. The PR does not logs that the branch has been force pushed, but if I click at the link to the branch associated with this PR, I can see the updated commits in there. Closing this unfortunately :-(

@fl4via fl4via closed this Jun 7, 2023
@fl4via
Copy link
Member Author

fl4via commented Jun 7, 2023

(github is also not showing options for reopening the PR)

@fl4via fl4via removed waiting PR update Awaiting PR update(s) from contributor before merging failed CI Introduced new regession(s) during CI check maintenance branch Targeting maintainance branch labels Jun 7, 2023
@fl4via fl4via added the duplicate Duplicates other pull request(s) label Jun 7, 2023
@fl4via
Copy link
Member Author

fl4via commented Jun 7, 2023

Duplicated by #1491

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicates other pull request(s)
Projects
None yet
1 participant