-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
OkHttp
reports leaked connections with versions 6.5.0
& 6.5.1
#4988
Comments
OkHttp
reports leaked connections with versions **6.5.0** & **6.5.1**OkHttp
reports leaked connections with versions *6.5.0* & *6.5.1*
OkHttp
reports leaked connections with versions *6.5.0* & *6.5.1*OkHttp
reports leaked connections with versions 6.5.0
& 6.5.1
More than likely this is due to moving the retry logic to a common place. Non-exceptional requests that return a 500+ code are probably not being formally closed prior to the retry. |
@shawkins wow, indeed, I don't observe leaking connection messages when instructing |
@rdesgroppes the fix should be straight-forward - #4990 |
Describe the bug
I gave a try bumping our project's
kubernetes-client
from version 6.4.1 to 6.5.0, then to 6.5.1. In both cases,OkHttp
started logging warnings while running some of our (informer-based) tests:When enabling a more fine-grained log level (more or less) as advised, the captured stack trace looks like:
... or, less often, when triggered from within the test thread, a more verbose:
Fabric8 Kubernetes Client version
6.5.1
Steps to reproduce
(trying to narrow down the problem - will update the ticket if I manage to provide reproducible steps)
Expected behavior
No leaked connection.
Runtime
other (please specify in additional context)
Kubernetes API Server version
other (please specify in additional context)
Environment
Linux
Fabric8 Kubernetes Client Logs
No response
Additional context
KubernetesMockServer
provided byio.fabric8:kubernetes-server-mock:6.5.1
,The text was updated successfully, but these errors were encountered: