[jbosstools-issues] [JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion

[Marián Labuda (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marián Labuda closed JBIDE-12098.
---------------------------------



Not happening in JBT 4.2.0.Alpha1. And marked as out-of-date. Closing.
                
> OpenShift Explorer: Timeout exception when forcing domain deletion
> ------------------------------------------------------------------
>
>                 Key: JBIDE-12098
>                 URL: https://issues.jboss.org/browse/JBIDE-12098
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.CR1
>            Reporter: Stefan Bunciak
>            Assignee: Andre Dietisheim
>             Fix For: 4.2.0.Alpha1
>
>         Attachments: deletedomain.png
>
>
> Tried to force domain deletion while having (medium geared) application on OpenShift.
> Screenshot:
> !deletedomain.png|thumbnail!
> Stack trace:
> {code}
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out
> 	at com.openshift.internal.client.RestService.request(RestService.java:109)
> 	at com.openshift.internal.client.RestService.request(RestService.java:89)
> 	at com.openshift.internal.client.RestService.request(RestService.java:74)
> 	at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> 	at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329)
> 	at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166)
> 	at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira