无法从守护程序接收消息。

Question

无法从守护程序接收消息。

4

我正在尝试设置使用Jenkins文件的Jenkins多分支管道。我正在使用Gradle构建项目，在Jenkins文件中，我有以下片段：

阶段（'build'）
  sh“./gradlew build --stacktrace”

每次运行构建时，它总是失败，并显示以下错误。我已尝试禁用Gradle守护程序，但仍显示相同的错误。

FAILURE: Build failed with an exception.

* What went wrong:
Could not receive a message from the daemon.

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.launcher.daemon.client.DaemonConnectionException: Could not receive a message from the daemon.
at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(DaemonClientConnection.java:81)
at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(DaemonClientConnection.java:35)
at org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:210)
at org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:178)
at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:141)
at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:92)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51)
at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:285)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:258)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:251)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:185)
at org.gradle.launcher.Main.doAction(Main.java:36)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:31)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:108)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Caused by: org.gradle.internal.remote.internal.RecoverableMessageIOException: Could not read message from '/127.0.0.1:33449'.
at org.gradle.internal.remote.internal.inet.SocketConnection.receive(SocketConnection.java:86)
at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(DaemonClientConnection.java:75)
... 29 more
Caused by: java.io.StreamCorruptedException: invalid stream header: ED000573
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:857)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:349)
at org.gradle.internal.io.ClassLoaderObjectInputStream.<init>(ClassLoaderObjectInputStream.java:27)
at org.gradle.internal.serialize.ExceptionReplacingObjectInputStream.<init>(ExceptionReplacingObjectInputStream.java:39)
at org.gradle.internal.serialize.Message.receive(Message.java:54)
at org.gradle.internal.serialize.BaseSerializerFactory$ThrowableSerializer.read(BaseSerializerFactory.java:240)
at org.gradle.internal.serialize.BaseSerializerFactory$ThrowableSerializer.read(BaseSerializerFactory.java:238)
at org.gradle.internal.logging.serializer.LogEventSerializer.read(LogEventSerializer.java:56)
at org.gradle.internal.logging.serializer.LogEventSerializer.read(LogEventSerializer.java:26)
at org.gradle.internal.serialize.DefaultSerializerRegistry$TaggedTypeSerializer.read(DefaultSerializerRegistry.java:144)
at org.gradle.launcher.daemon.protocol.DaemonMessageSerializer$OutputMessageSerializer.read(DaemonMessageSerializer.java:147)
at org.gradle.launcher.daemon.protocol.DaemonMessageSerializer$OutputMessageSerializer.read(DaemonMessageSerializer.java:133)
at org.gradle.internal.serialize.DefaultSerializerRegistry$TaggedTypeSerializer.read(DefaultSerializerRegistry.java:144)
at org.gradle.internal.serialize.Serializers$StatefulSerializerAdapter$1.read(Serializers.java:36)
at org.gradle.internal.remote.internal.inet.SocketConnection.receive(SocketConnection.java:79)
... 30 more

- Wins

5个回答

2

of all: which gradle version (I got this since upgrading from 4.7 to 4.9, but your post is much older)
please try to build without daemon, i.e.
```
sh "./gradlew --no-daemon build -s"
```
this should indicate what is the error cause, typically (my observation) there are errors thrown in (custom)plugins or scripts of initialization phase (buildSrc)

- childno͡.de

谢谢，这帮助我找到了根本原因。 - ror

2

我遇到了由VMware软件引起的错误。如果您正在使用Windows 10，并且同时使用VMware或最近下载了它，这是我的解决方案：

打开任务管理器。
终止所有与VMware相关的服务。

- Hajime

0

设置环境变量_JAVA_OPTIONS的值为-Djava.net.preferIPv4Stack=true。

Windows命令： set _JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true

来源：https://github.com/gradle/gradle/issues/16996#issuecomment-910296681

- Krutyi 4el

-2

关闭您的电脑热点，然后重试。

- Zhou W.L.

这是与另一个答案相同的解决方案。 - Eric Aya

网页内容由stack overflow 提供, 点击上面的

可以查看英文原文，
原文链接

- Jose Antonio Dominguez Garcia · Accepted Answer

您的移动热点启用了吗？如果您使用的是Windows 10的移动热点功能，在我的电脑上可能会出现错误，建议先禁用并重试，通常可以正常运行。