[jbosstools-issues] [JBoss JIRA] (JBIDE-24831) Race condition between launching minishift and adding debug listener

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-24831:
-------------------------------------

This is most easily replicatable by using 'kvm' when your system doesn't have kvm. Output would quickly result in something like this:

{code}
Starting local OpenShift cluster using 'kvm' hypervisor...
E0808 10:38:15.319627   22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying.
E0808 10:38:15.320522   22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying.
E0808 10:38:15.320598   22808 start.go:172] Error starting the VM: Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?. Retrying.
Error starting the VM:  Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?
Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?
Driver "kvm" not found. Do you have the plugin binary "docker-machine-driver-kvm" accessible in your PATH?
{code}

Then the process terminates, before the listener has been added, and the server is stuck in 'starting' mode. 

> Race condition between launching minishift and adding debug listener
> --------------------------------------------------------------------
>
>                 Key: JBIDE-24831
>                 URL: https://issues.jboss.org/browse/JBIDE-24831
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.5.0.Final
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.5.1.AM1
>
>
> The current code does the following:
>   1) Launch the process
>   2) Then add the debugListener to o.e.debug
> This is problematic. If the process ends very quickly,. our listener will never get alerted that the process terminated, and so the server will be stuck at 'starting'. 
> Solution is to add the debugListener BEFORE launching the process. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)