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

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-21797:
---------------------------------------

I haven't seen this problem for some time now. But I was using vagrant 1.7 and you're saying it was caused by changes in vagrant 1.8.1 output. So I updated to vagrant 1.8.1 now and it still works for me. Closing.

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