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

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-22129:
---------------------------------------

yes. This is expected since we are trying to get a project and it doesn't exist. The server on purpose returns 403 instead of 404

> 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)