[jbosstools-issues] [JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

[Jeff MAURY (JIRA)]

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

Jeff MAURY commented on JBIDE-22604:
------------------------------------

The server is never switch to started because the Eclipse debug framework never switch the associated RuntimeProcess to terminated because the Eclipse debug framework will first close the associated stream proxys and it appears that the outputstream of the vagrant process is never detected closed so we got a deadlock and as the Eclipse debug framework never switch to terminated so the server never switch to started so...
I created a gist that demonstrate the user case: https://gist.github.com/jeffmaury/ba61c91fe910220585e9893540ccec7d
The first argument is the path of the vagrant bin
The second argument is the path of the CDK folder (where the Vagrant file is)
The third argument is the user for registration
The fourth argument is the password for registration
If run with CDKv2, then threads end and launcher exits
If the with cdk 2.1rc2, then threads do no end and launcher stays alive

> CDK server adapter stuck at starting
> ------------------------------------
>
>                 Key: JBIDE-22604
>                 URL: https://issues.jboss.org/browse/JBIDE-22604
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.0.Final
>         Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
> devstudio 10.0.0.GA-a
> CDK 2.1.RC3
>            Reporter: Jan Richter
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 4.4.0.Final
>
>
> I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'.
> In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. 
> Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop.



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