[jbosstools-issues] [JBoss JIRA] (JBIDE-22861) Explorer: Pod is not refreshed (watch problem with new ohttp based rest client)

[Jeff Cantrill (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13275960#comment-13275960 ] 

Jeff Cantrill commented on JBIDE-22861:
---------------------------------------

A new WatchClient is created https://github.com/openshift/openshift-restclient-java/blob/master/src/main/java/com/openshift/internal/restclient/DefaultClient.java#L101 everytime we call watch.  Additionally, when we actually start the watch https://github.com/openshift/openshift-restclient-java/blob/master/src/main/java/com/openshift/internal/restclient/okhttp/WatchClient.java#L101 we essentially clone the underlying okClient which should handle the case we have with JBT.  Additionally, the way we utilize the watchclient, we create one for each kind per project which means in theory we should never get to the limit of 10.  Best I can understand from the API, https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/OkHttpClient.java#L838 and https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/Dispatcher.java#L77 and https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/Dispatcher.java#L98 the settings we have as our defaults are sufficient.  I will investigate to see if i can resolve.

> Explorer: Pod is not refreshed (watch problem with new ohttp based rest client)
> -------------------------------------------------------------------------------
>
>                 Key: JBIDE-22861
>                 URL: https://issues.jboss.org/browse/JBIDE-22861
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.AM2
>            Reporter: Andre Dietisheim
>            Assignee: Jeff Cantrill
>             Fix For: 4.4.1.AM3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)