[
https://issues.jboss.org/browse/JBIDE-23046?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-23046.
---------------------------------
It would be really nice to be able to verify this, but currently it seems nobody can
reproduce the timeout issue - JBIDE-22818 and CDK-4 . So I don't see how I could
verify this.
[~rob.stryker], do you have a suggestion? For now, I'm closing this.
If call to vagrant service-manager times out, openshift / docker
connect should still try to be created
-------------------------------------------------------------------------------------------------------
Key: JBIDE-23046
URL:
https://issues.jboss.org/browse/JBIDE-23046
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, server
Affects Versions: 4.4.1.AM3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.4.1.Final
In Windows, I was experiencing an error where the call to vagrant service-manager was not
completing. This wasn't due to the output being unavailable, but rather the process
not terminating. The current code throws a TimeoutException, but makes no attempt to
check if the output is enough to still create the docker / openshift connections.
The code should attempt to survive the error and continue along.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)