[jbosstools-issues] [JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

[Marián Labuda (JIRA)]

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

Marián Labuda commented on JBIDE-22129:
---------------------------------------

I see following output in tracing log when deleting a project
{code}| Worker-676 | 2016-04-12 17:40:48.362 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Deleting resource https://10.1.2.2:8443/oapi/v1/projects/newproject |
| Worker-676 | 2016-04-12 17:40:48.384 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | {
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Success",
  "code": 200
}
 |
| Worker-676 | 2016-04-12 17:40:48.384 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Built url: https://10.1.2.2:8443/oapi/v1/projects/newproject |
| Worker-676 | 2016-04-12 17:40:48.416 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | {"kind":"Project","apiVersion":"v1","metadata":{"name":"newproject","selfLink":"/oapi/v1/projects/newproject","uid":"e3b2bd19-00c4-11e6-bf0a-525400b46e1a","resourceVersion":"3328","creationTimestamp":"2016-04-12T15:40:31Z","deletionTimestamp":"2016-04-12T15:40:47Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/sa.scc.mcs":"s0:c10,c5","openshift.io/sa.scc.supplemental-groups":"1000100000/10000","openshift.io/sa.scc.uid-range":"1000100000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Terminating"}}
 |
| Worker-676 | 2016-04-12 17:40:48.917 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Built url: https://10.1.2.2:8443/oapi/v1/projects/newproject |
| Worker-676 | 2016-04-12 17:40:48.929 | org.jboss.tools.openshift.client | /debug/client | org.jboss.tools.openshift.client.internal.log.Trace | trace | 86 | Could not get resource newproject in namespace : {
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "User \"openshift-dev\" cannot get projects in project \"newproject\"",
  "reason": "Forbidden",
  "details": {
    "name": "newproject",
    "kind": "projects"
  },
  "code": 403
}
{code}

I suppose its ok, bcs there is no other watcher connected nor after some time there is any watching. But should there be that failure of getting deleted project? 

> Watches should not try to reconnect when a project has been deleted
> -------------------------------------------------------------------
>
>                 Key: JBIDE-22129
>                 URL: https://issues.jboss.org/browse/JBIDE-22129
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Fred Bricon
>            Assignee: Jeff Cantrill
>              Labels: respin-b
>             Fix For: 4.3.1.CR1
>
>
> When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). 
> After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying.
> Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch 



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