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

Infinite Loop When Channels Leak #514

Merged
merged 4 commits into from
Aug 5, 2023

Conversation

guillermocalvo
Copy link
Contributor

Closes #295

@sdelamo
Instead of throwing an exception as the issue suggests, the connection pool will return null.

getChannel makes no promises about nullability, so I think this should be safe.

Please let me know if you rather throw an IOException.

@guillermocalvo guillermocalvo added the type: bug Something isn't working label Aug 2, 2023
@guillermocalvo guillermocalvo linked an issue Aug 2, 2023 that may be closed by this pull request
@sonarcloud
Copy link

sonarcloud bot commented Aug 4, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@sdelamo sdelamo merged commit 257a843 into master Aug 5, 2023
@sdelamo sdelamo deleted the 295-infinite-loop-when-channels-leak branch August 5, 2023 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Infinite Loop When Channels Leak
2 participants