You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I start my server locally and perform load testing on it, maybe my load test code does not work well yet but I see the warning log which like:
16:20:14.628 [OkHttp ConnectionPool] WARN okhttp3.OkHttpClient - A connection to https://beta-indico.xxx.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);
And I see that the OkHttpClient is used in IndicoKtorClient#L26, so I wonder perhaps there is something went wrong in the code when it request to Indico instance internal api?
The text was updated successfully, but these errors were encountered:
denglitong
changed the title
okhttp3.OkHttpClient warning: A connection to https://beta-indico.xxx.com/ was leaked
IndicoKtorClient okhttp3.OkHttpClient warning: A connection to https://beta-indico.xxx.com/ was leaked
Dec 28, 2021
I found in AuthorizationInterceptor.java#L39, the client requests twice but don't close responses finally. Maybe it's the reason why the connection leaked.
I start my server locally and perform load testing on it, maybe my load test code does not work well yet but I see the warning log which like:
16:20:14.628 [OkHttp ConnectionPool] WARN okhttp3.OkHttpClient - A connection to https://beta-indico.xxx.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);
And I see that the OkHttpClient is used in IndicoKtorClient#L26, so I wonder perhaps there is something went wrong in the code when it request to Indico instance internal api?
The text was updated successfully, but these errors were encountered: