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.

Sign up for GitHub

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

Jump to bottom

OkHttpClient connection was leaked warning #6

Closed
z4kn4fein opened this issue Jan 11, 2021 · 2 comments
Closed

OkHttpClient connection was leaked warning #6

z4kn4fein opened this issue Jan 11, 2021 · 2 comments
Assignees
@z4kn4fein

Comments

@z4kn4fein
Copy link
Member

Investigate this warning:

2021-01-10 23:25:45.108 WARN 61 --- [ ConnectionPool] okhttp3.OkHttpClient : A connection to https://cdn-global.configcat.com/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
@z4kn4fein z4kn4fein self-assigned this Jan 11, 2021
z4kn4fein added a commit that referenced this issue Jan 11, 2021
@z4kn4fein
Fix for #6, close https response body properly
d3eaf4c
@z4kn4fein
Copy link
Member Author

It seems the response body must be closed every time, regardless of the response status code. More info: square/okhttp#2311

@z4kn4fein
Copy link
Member Author

Fix released in v6.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@z4kn4fein z4kn4fein

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@z4kn4fein