java - gradle 命令失败，因为它无法启动守护进程

Question

我正在尝试运行 gradle 命令。这最初有效。但是一段时间后它开始失败，因为它无法启动守护进程。我在 Windows 7 Enterprise 上使用 Gradle 2.5 和 IBM jdk 1.6。

我已经清理了我的用户主目录中的 .gradle 目录并重新启动了我的系统。

这在我 friend 的机器上运行良好，版本相同。请帮忙。

org.gradle.api.GradleException: Could not start Gradle daemon.        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:137)        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:114)        at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:109)        at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:87)        at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:117)        at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:77)        at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:40)        at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:170)        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)        at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)        at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)        at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)        at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)        at org.gradle.launcher.Main.doAction(Main.java:33)        at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)        at java.lang.reflect.Method.invoke(Method.java:611)        at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)        at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)        at org.gradle.launcher.GradleMain.main(GradleMain.java:23)Caused by: org.gradle.api.UncheckedIOException: java.io.EOFException        at org.gradle.launcher.daemon.bootstrap.DaemonStartupCommunication.readDiagnostics(DaemonStartupCommunication.java:100)        at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:40)        at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:133)        ... 24 moreCaused by: java.io.EOFException        at java.io.DataInputStream.readBoolean(DataInputStream.java:238)        at org.gradle.internal.serialize.InputStreamBackedDecoder.readBoolean(InputStreamBackedDecoder.java:47)        at org.gradle.internal.serialize.AbstractDecoder.readNullableString(AbstractDecoder.java:53)        at org.gradle.launcher.daemon.bootstrap.DaemonStartupCommunication.readDiagnostics(DaemonStartupCommunication.java:85)        ... 26 more

Answer 1

不确定您的场景(以及 IBM jdk)，但每当守护进程或任何其他完美工作的构建突然停止为我工作时，我会尝试两种方法。

1. gradle myTask --no-daemon 在没有守护进程的情况下运行构建，以确保它是否确实是守护进程的问题。

2. gradle --stop 终止任何现有守护进程，然后再次尝试构建。

在 gradle docs 中有关于在 Windows 上使用守护进程的警告。 :

It is also possible to destabilize the Daemon (and build environment in general) by running builds that do not release resources correctly. This is a particularly poignant problem when using Microsoft Windows as it is less forgiving of programs that fail to close files after reading or writing.