[jbosstools-issues] [JBoss JIRA] (JBIDE-21294) NPE when starting CDK server

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-21294:
---------------------------------------

There is now a proper error message in place, great!
{code}
Unable to locate vagrant command. Please check to ensure that the command is available on your Path environment variable.
{code}

To answer your question about tracing.
I found out why it worked for me in one instance and not the other - as discussed previously, PATH is not set up when you start Eclipse by double-clicking the app in Finder. But when I run the JBDS installer from command line (which I usually do) and then after installation the installer launches JBDS for me, it will inherit PATH, so during runtime detection, the path to vagrant is set up correctly and it works until you restart your IDE. I logged JBIDE-21315 to track this issue.

But the NPE is solved so this JIRA can be closed.

> NPE when starting CDK server
> ----------------------------
>
>                 Key: JBIDE-21294
>                 URL: https://issues.jboss.org/browse/JBIDE-21294
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.Beta1
>
>
> I've been testing the CDK adapter with [1] today and when I tried to start again from scratch (vagrant destroy + new workspace) and added the server again and started, I got a NPE:
> {code}
> An internal error occurred during: "Starting cdk-v2 CDK Server".
> java.lang.NullPointerException
> 	at java.io.File.<init>(File.java:277)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:133)
> 	at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> 	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I did add the user credentials in the server editor.
> Now I looked in the launch config and the first field at the top is empty - it should contain path to vagrant. I'm not sure why it's missing - I just used runtime detection. But in any case, the NPE should be handled somehow.
> [1] https://github.com/redhat-developer-tooling/openshift-vagrant



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