[GRADLE-2316] Received invalid response from the daemon Created: 18/May/12  Updated: 05/Sep/15  Resolved: 05/Sep/15

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.7-rc-2

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Fixed Votes: 3


Random error while executing a compile job. I as yet not found a rhyme or reason as to why it happens.

Executing the build again resolves the issue.

Environment: CentOS 6.2
Java: 1.6 u24

  • Exception is:
    java.lang.IllegalStateException: Received invalid response from the daemon: 'Build {id=1337268822092-1, currentDir=/opt/redprairie/dev/mnt-citools}' is a result of a type we don't have a strategy to handle.Earlier, 'Build{id=1337268822092-1, currentDir=/opt/redprairie/dev/mnt-citools}

    ' request was sent to the daemon.
    at org.gradle.launcher.daemon.client.DaemonClient.invalidResponse(DaemonClient.java:195)
    at org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:138)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:108)
    at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:56)
    at org.gradle.launcher.cli.DaemonBuildAction.run(DaemonBuildAction.java:50)
    at org.gradle.launcher.cli.ActionAdapter.execute(ActionAdapter.java:30)
    at org.gradle.launcher.cli.ActionAdapter.execute(ActionAdapter.java:22)
    at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:201)
    at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:174)
    at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:170)
    at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:139)
    at org.gradle.launcher.exec.ExceptionReportingAction.execute(ExceptionReportingAction.java:31)
    at org.gradle.launcher.exec.ExceptionReportingAction.execute(ExceptionReportingAction.java:20)
    at org.gradle.launcher.Main.doAction(Main.java:48)
    at org.gradle.launcher.exec.EntryPoint.run(EntryPoint.java:45)
    at org.gradle.launcher.Main.main(Main.java:39)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.gradle.launcher.ProcessBootstrap.runNoExit(ProcessBootstrap.java:50)
    at org.gradle.launcher.ProcessBootstrap.run(ProcessBootstrap.java:32)
    at org.gradle.launcher.GradleMain.main(GradleMain.java:24)

Build step 'Invoke Gradle script' changed build result to FAILURE

Comment by Gradle Forums [ 18/May/12 ]

Does the class `handle.Earler` mean anything to you? It's not part of the Gradle codebase. Very strange that it's getting into the Daemon infrastructure.

Comment by Gradle Forums [ 18/May/12 ]

You mean: handle.Earlier? It's not a class - it's a regular english sentence

I have this problem on my radar, I've seen this on CI. Exporting to JIRA.

Comment by Joshua Wiens [ 18/May/12 ]

Jenkins ver. 1.462 to be specific

Comment by Kris De Volder [ 27/Jun/12 ]

I keep getting this error fairly frequently on STS Gradle tooling regression tests which is causing spurious test failures. Still in 1.0 final as well.

Comment by Jem Mawson [ 23/Sep/12 ]

I'm seeing this error 1 times out of every 10 or 20 builds - on Jenkins builds only. (Jenkins v1.481). Seen with both Gradle 1.1 and 1.2.

Comment by Szczepan Faber [ 26/Aug/15 ]

We're seeing this problem once per ~15 builds, for one project, on different machines (all mac's with yosemite). There is nothing obvious in the logs. We debugged but could not find a root cause. Why would the daemon reflect back to the client the 'build' request? The problem seems to be low level, perhaps related to the messaging infrastructure the daemon uses to talk to the gradle client? We're using Gradle 2.4, we will try the latest.

Generated at Wed Jun 30 12:18:38 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.