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

Consider ClosedChannelException as well when checking for connection abort #5394

Conversation

BalusC
Copy link
Contributor

@BalusC BalusC commented Feb 10, 2024

@BalusC BalusC added this to the 4.0.6 milestone Feb 10, 2024
Copy link
Contributor

@mnriem mnriem left a comment

Choose a reason for hiding this comment

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

Approving, but would have loved to see a test ;)

@BalusC
Copy link
Contributor Author

BalusC commented Feb 17, 2024

Mojarra doesn't anymore have IT env (everything has been moved to Faces/TCK) and current UT env is super outdated with JUnit4/Easymock/Powermock, should become JUnit5/Mockito.

@BalusC BalusC merged commit 6189930 into 4.0 Mar 2, 2024
3 checks passed
@BalusC BalusC deleted the mojarra_issue_5391_consider_ClosedChannelException_as_well_when_checking_for_connection_abort branch March 2, 2024 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants