Skip to content

Close connections asynchronously (2) #134

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

Merged
merged 12 commits into from
Apr 24, 2025
Merged

Close connections asynchronously (2) #134

merged 12 commits into from
Apr 24, 2025

Conversation

rbygrave
Copy link
Member

No description provided.

@rbygrave
Copy link
Member Author

I'm good with this @rPraml . I plan to maybe do a followup PR which replaces the Timer with something that gives the option of using a Java 21 Virtual Thread instead

And regardless of how well close executes/fails/slow etc
- Start on pool creation
- Stop on fullShutdown of pool
- ExecutorService becomes final
To protect against a possible race condition between a shutdown hook invocation and application code invocation.
@rbygrave
Copy link
Member Author

Ok, I reckon this is good. I'll merge @rPraml and we can adjust afterwards if you see something.

@rbygrave rbygrave merged commit fcd8493 into master Apr 24, 2025
2 checks passed
@rbygrave rbygrave deleted the feature/close-async-2 branch April 24, 2025 05:02
@rbygrave rbygrave modified the milestones: 9.6, 9.7 Apr 24, 2025
@rbygrave rbygrave linked an issue Apr 24, 2025 that may be closed by this pull request
@rPraml
Copy link
Collaborator

rPraml commented Apr 24, 2025

@rbygrave Thanks for reviewing and merging

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.

Long running close on wrapped connection may block pool.
2 participants