[
https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi...
]
Jeff MAURY commented on JBIDE-23006:
------------------------------------
Seems to be related to the first exchanges made with Openshift. If your Openshift
connection is defined without password stored, then you will get the credential dialog and
you will get 2 leaks detected. If your Openshift connection is defined with a password,
then you will get only 1 leak which seem logical as you will have two initial exchanges if
your password is not stored.
I added a throwable object to the leak mechanism in okhttp in order to display the
stacktrace of the allocation path but didn't figure why the leak appears but found
several places where Response objects are not closed. Fixing didn't remove the
message(s)
OkHttp reports leaked connections
---------------------------------
Key: JBIDE-23006
URL:
https://issues.jboss.org/browse/JBIDE-23006
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM3
Reporter: Fred Bricon
Assignee: Jeff MAURY
Fix For: 4.4.1.Final
After connecting to an OpenShift instance, some warnings show up in the logs eventually:
{noformat}
août 15, 2016 10:55:20 AM okhttp3.internal.Platform log
AVERTISSEMENT: A connection to
https://console.dev-preview-stg.openshift.com/ was leaked.
Did you forget to close a response body?
août 15, 2016 10:55:20 AM okhttp3.internal.Platform log
AVERTISSEMENT: A connection to
https://console.dev-preview-stg.openshift.com/ was leaked.
Did you forget to close a response body?
{noformat}
I haven't figured out exactly what steps cause these yet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)