[
https://issues.jboss.org/browse/JBIDE-23511?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-23511:
-------------------------------------
So I've tested this extensively, and there's nothing we can really do here. Once
it times out, wtp tells the server adapter to stop. I can't really tell at that moment
the difference between a failed startup or an actual shutdown call.
Since this ssl popup is happening in the poller, we can't get an answer as to whether
openshift is up or not, so we don't know whether to mark the server as started or wait
a bit longer. When timeout comes, it's too late to do anything about it.
The only way to really handle it is to get rid of the check for openshift health... but we
put that in because people weren't being alerted to potential problems with openshift
starting up.
This is such a minor issue and since ti applies to all server adapters, and can't be
fixed, I'm just going to reject it.
CDK start fails if you don't accept OpenShift certificate in
time
-----------------------------------------------------------------
Key: JBIDE-23511
URL:
https://issues.jboss.org/browse/JBIDE-23511
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.2.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.5.0.AM1
This happened to me a couple of times and it's pretty annoying, but I'm not sure
if anything can be done about it.
When you launch cdk in devstudio and then forget about it and do something else, then
when you get back to devstudio to actually play with cdk, you will see it fail horribly.
This is because the startup time out has been reached and since you haven't accepted
the openshift certificate, the prompt will be waiting for you and will cause time out.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)