[jbosstools-issues] [JBoss JIRA] (JBIDE-21797) Fails to start the CDK server when it's was already started from CLI

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-21797:
-------------------------------------

I'm unable to replicate :(   It seems to WorkForMe. 

Tracing into CDKLaunchCOntroller around line 156 has the following code:

{code}
		IStatus stat = new VagrantPoller().getCurrentStateSynchronous(getServer());
		if( stat.isOK()) {
			beh.setServerStarted();
			return;
		}
{code}

VagrantPoller.onePing is a good place to investigate further, but again, it seems to be functioning normally to me. 

> Fails to start the CDK server when it's was already started from CLI
> --------------------------------------------------------------------
>
>                 Key: JBIDE-21797
>                 URL: https://issues.jboss.org/browse/JBIDE-21797
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.3.1.CR1
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>             Fix For: 4.3.1.CR1
>
>
> - Start the CDK (version from http://cdk-builds.usersys.redhat.com/builds/19-Feb-2016/) from CLI
> - once it's started, start the same CDK from the CDK server adapter
> => the server should detect the CDK already started and should simply be put in started mode, instead it fails to start with 
> !http://content.screencast.com/users/fbricon/folders/Jing/media/9674437e-12fa-4523-9d42-69e0e4302be7/00000345.png|width=650!



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