[jbosstools-issues] [JBoss JIRA] (JBIDE-23265) Can't start CDK server if user or password env var is empty

Martin Malina (JIRA) issues at jboss.org
Mon Oct 24 11:05:00 EDT 2016


     [ https://issues.jboss.org/browse/JBIDE-23265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-23265.
---------------------------------


Verified in devstudio-10.2.0.AM3-v20161024-1202-B6286-installer-standalone.jar 

> Can't start CDK server if user or password env var is empty
> -----------------------------------------------------------
>
>                 Key: JBIDE-23265
>                 URL: https://issues.jboss.org/browse/JBIDE-23265
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.2.AM1
>            Reporter: Jeff MAURY
>            Assignee: Rob Stryker
>              Labels: cdk, server
>             Fix For: 4.4.2.AM3
>
>
> If the user or password env var name is empty, then server refuses to start. The error is the following:
> !ENTRY org.jboss.tools.openshift.cdk.server.core 4 0 2016-09-26 11:29:46.973
> !MESSAGE Exec_tty error:Cannot run program "C:\Apps\HashiCorp\Vagrant\bin\vagrant.exe": Unknown reason
> !STACK 0
> java.io.IOException: Exec_tty error:Cannot run program "C:\Apps\HashiCorp\Vagrant\bin\vagrant.exe": Unknown reason
> 	at org.eclipse.cdt.utils.spawner.Spawner.exec_pty(Spawner.java:387)
> 	at org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:99)
> 	at org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:98)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(VagrantLaunchUtility.java:198)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(VagrantLaunchUtility.java:185)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(VagrantLaunchUtility.java:178)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:201)
> 	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)



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


More information about the jbosstools-issues mailing list