okHttp is complaining about leaking connections, response was not closed

[adietish]

in user programs that use the openshift-restclient-java one can see the following log entries:

16:11:43,536 WARNING [okhttp3.OkHttpClient] (OkHttp ConnectionPool) A connection to https://xxxx.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);

[adietish]

the same problem was spotted and fixed for m2e/aether-connector: takari/aether-connector-okhttp#12

[jeffmaury]

@adietish do you know how to reproduce it in JBossTools ?

[adietish]

@jeffmaury I create an eap app on employee.openshift.com, have the source imported and the server adapter created. Then I hit "Publish" in the server ctx menu and wait for it to be finished. At some point the following shows up in the Eclipse log:

Sep 04, 2019 3:32:44 PM okhttp3.internal.platform.Platform log
WARNING: A connection to https://console.rh-us-east-1.openshift.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);
Sep 04, 2019 3:32:44 PM okhttp3.internal.platform.Platform log
WARNING: A connection to https://console.rh-us-east-1.openshift.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);

[jeffmaury]

Yes found a way to reproduce. Then switch to the new lib but this is still hapenning