-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
HttpService cause http connection leak #710
Labels
awaiting-pr
Waiting for PR
awaiting-user-input
Require more info or input from user
bug
A bug in behaviour or functionality
Comments
Please provide information to reproduce |
This is caused when an error is returned (okhttp throws an error if it's not 2xx) from the rpc endpoint. |
antonydenyer
added a commit
to antonydenyer/web3j
that referenced
this issue
Jun 4, 2019
should fix hyperledger-web3j#710 by implementing square/okhttp#2311
antonydenyer
added a commit
to antonydenyer/web3j
that referenced
this issue
Jun 4, 2019
should fix hyperledger-web3j#710 by implementing square/okhttp#2311
antonydenyer
added a commit
to antonydenyer/web3j
that referenced
this issue
Jun 4, 2019
should fix hyperledger-web3j#710 by implementing square/okhttp#2311
This is still an open issue. The change I made didn't solve the issue and was reverted. |
This was auto-closed from the merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
awaiting-pr
Waiting for PR
awaiting-user-input
Require more info or input from user
bug
A bug in behaviour or functionality
application log
okhttp3.OkHttpClient - A connection to http://localhost:8545/ 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);
==============
okhttp3 java doc
okhttp3.ResponseBody
A one-shot stream from the origin server to the client application with the raw bytes of the response body. Each response body is supported by an active connection to the webserver. This imposes both obligations and limits on the client application.
The response body must be closed.
Each response body is backed by a limited resource like a socket (live network responses) or an open file (for cached responses). Failing to close the response body will leak resources and may ultimately cause the application to slow down or crash.
The text was updated successfully, but these errors were encountered: