Some things to check:

• When you run this in Eclipse is the daemon running after you get the exception? (ie is it a problem starting the daemon, or connecting to the daemon? )
• Are you able to run something like 'gradle --daemon tasks' for this project from the command-line?

How do I check if the Daemon is running?
I did see some messages like "Warning Gradle daemon is experimental...". Is that printed by the daemon?

I'll give the commandline stuff a try, report back later on.

I've installed the Gradle commandline tools on the windows box (latest snapshot drop from artifactory):

http://repo.gradle.org/gradle/distributions/gradle-snapshots/gradle-1.0-milestone-4-20110512131549+1000-bin.zip

when I do "gradle --daemon" I get this:

C:\Documents and Settings\kdvolder\Desktop\Dropbox\Dropbox\resources\projects\he
lloWorldTask>gradle --daemon
Note: the Gradle build daemon is an experimental feature.
As such, you may experience unexpected build failures. You may need to occasiona
lly stop the daemon.

FAILURE: Build failed with an exception.

* What went wrong:
Timeout waiting to connect to Gradle daemon.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

Also ran it with the suggested debug options:

C:\Documents and Settings\kdvolder\Desktop\Dropbox\Dropbox\resources\projects\he
lloWorldTask>gradle --daemon --stacktrace --debug
11:43:28.811 [WARN] [org.gradle.launcher.DaemonClient] Note: the Gradle build da
emon is an experimental feature.
11:43:28.811 [WARN] [org.gradle.launcher.DaemonClient] As such, you may experien
ce unexpected build failures. You may need to occasionally stop the daemon.
11:43:28.874 [INFO] [org.gradle.launcher.DaemonConnector] Starting Gradle daemon

11:43:59.030 [ERROR] [org.gradle.BuildExceptionReporter]
11:43:59.046 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build failed w
ith an exception.
11:43:59.061 [ERROR] [org.gradle.BuildExceptionReporter]
11:43:59.061 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
11:43:59.061 [ERROR] [org.gradle.BuildExceptionReporter] Timeout waiting to conn
ect to Gradle daemon.
11:43:59.077 [ERROR] [org.gradle.BuildExceptionReporter]
11:43:59.077 [ERROR] [org.gradle.BuildExceptionReporter] * Try:
11:43:59.077 [ERROR] [org.gradle.BuildExceptionReporter] Run with --stacktrace o
ption to get the stack trace. Run with --info or --debug option to get more log
output.

Hey,

I'm having troubles reproducing the problem.

1. I tried various firewall/proxy configurations on my Windows 7 and mac with milestone-3 and the latest snapshot
2. I checked on friend's laptop who has a typical corporate laptop with win XP and authenticated network proxy - worked fine.

Can you share some more details about your environment that can help me reproduce it?

It is a view on a Windows XP VM running behind a proxy firewall.

It could be something in the setup of that machine. But to be honest I'm not sure what info to provide.
If there's something specific you'd like me to check I can do it.

It could very well be that the problem isn't Gradle but somehow the machine's proxy configuration isn't quite setup correctly.

If you can't reproduce it, I wouldn't worry too much about it. Just close the bug as 'cannot reproduce'.

I cannot seem to reproduce this issue.

One of our user just reported experiencing this kind of problem in STS using milestone 6 snapshot of Gradle.

https://issuetracker.springsource.com/browse/STS-2287

Maybe this issue should be reopened. I've asked the user to try to provide more details here.

Please provide more info if possible. Thanks!

All that I can provide, which may or may not be relevant...

It seems that both cases where there was a problem involved a Windows 32 bit environment.
The user who reported the problem against STS mentioned explicitly testing also with Ubuntu and not having the problem. So it could be the problem is Windows specific.

Thanks Kris!

Hi ,
I am facing the same error and after some tracing i was able to fix it but I don not know exactly why it happen.
I fixed the issue by removing && potentialContext.getDaemonOpts().equals(desiredContext.getDaemonOpts() from DaemonCompatibilitySpec for some reason the DaemonOpts are not equal between desiredContext and potentialContext
below you can find the values for DaemonOpts

is equal java home true , is equal DaemonOpts false

@Osama, I suspect you're running into a different problem with the same symptom: http://issues.gradle.org/browse/GRADLE-2089

@Adam Thanks for your replay , yes the issue was because of IBM JDK. and it is fixed after switching to Oracle JDK

We're seeing a similar problem. We just added a new developer (we already have half a dozen or so), and he is unable to import to SpringSource's STS because of this issue. He's running Windows 7 64 bit and the latest Eclipse Indigo 64 bit. No one else has seen this issue.

We've cached the gradle-1.0-milestone-7-bin.zip file to a local server so that we don't have to deal with firewall issues. We've tried using native, manual, and direct network settings. We've restarted everything.

We are having no problem at the command line, but this consistently fails when trying to import from the SpringSource STS plugin to Eclipse.

Here's a stack trace of the error:

Still get the gradel error when I do it from home. It is the same timeout error: Timeout waiting to connect to Gradle daemon

java.lang.reflect.InvocationTargetException
at com.springsource.sts.gradle.core.util.GradleRunnable.run(GradleRunnable.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.core.runtime.CoreException: Timeout waiting to connect to Gradle daemon.
at com.springsource.sts.gradle.core.util.ExceptionUtil.coreException(ExceptionUtil.java:34)
at com.springsource.sts.gradle.core.util.ExceptionUtil.coreException(ExceptionUtil.java:45)
at com.springsource.sts.gradle.core.GradleModelProvider.buildModel(GradleModelProvider.java:363)
at com.springsource.sts.gradle.core.GradleModelProvider$GroupedModelProvider.ensureModels(GradleModelProvider.java:258)
at com.springsource.sts.gradle.core.GradleProject.getModelProvider(GradleProject.java:480)
at com.springsource.sts.gradle.core.GradleProject.getGradleModel(GradleProject.java:540)
at com.springsource.sts.gradle.core.GradleProject.getSkeletalGradleModel(GradleProject.java:565)
at com.springsource.sts.gradle.ui.wizards.GradleImportWizardPageOne$9.doit(GradleImportWizardPageOne.java:471)
at com.springsource.sts.gradle.core.util.GradleRunnable.run(GradleRunnable.java:77)
... 1 more
Caused by: org.gradle.tooling.GradleConnectionException: Could not fetch model of type 'HierarchicalEclipseProject' using Gradle distribution 'http://<local server>/images/3/37/Gradle-1.0-milestone-7-bin.zip'.
at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:46)
at org.gradle.tooling.internal.consumer.DefaultAsyncConnection$3.run(DefaultAsyncConnection.java:73)
at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.gradle.api.GradleException: Timeout waiting to connect to Gradle daemon.
at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:105)
at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:102)
at org.gradle.tooling.internal.provider.DaemonGradleLauncherActionExecuter.execute(DaemonGradleLauncherActionExecuter.java:44)
at org.gradle.tooling.internal.provider.DaemonGradleLauncherActionExecuter.execute(DaemonGradleLauncherActionExecuter.java:31)
at org.gradle.tooling.internal.provider.LoggingBridgingGradleLauncherActionExecuter.execute(LoggingBridgingGradleLauncherActionExecuter.java:56)
at org.gradle.tooling.internal.provider.LoggingBridgingGradleLauncherActionExecuter.execute(LoggingBridgingGradleLauncherActionExecuter.java:30)
at org.gradle.tooling.internal.provider.DefaultConnection.run(DefaultConnection.java:80)
at org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:73)
at org.gradle.tooling.internal.consumer.LazyConnection$3.run(LazyConnection.java:90)
at org.gradle.tooling.internal.consumer.LazyConnection$3.run(LazyConnection.java:88)
at org.gradle.tooling.internal.consumer.LazyConnection.withConnection(LazyConnection.java:98)
at org.gradle.tooling.internal.consumer.LazyConnection.getModel(LazyConnection.java:88)
at org.gradle.tooling.internal.consumer.ProgressLoggingConnection$2.run(ProgressLoggingConnection.java:61)
at org.gradle.tooling.internal.consumer.ProgressLoggingConnection$2.run(ProgressLoggingConnection.java:59)
at org.gradle.tooling.internal.consumer.ProgressLoggingConnection.run(ProgressLoggingConnection.java:74)
at org.gradle.tooling.internal.consumer.ProgressLoggingConnection.getModel(ProgressLoggingConnection.java:59)
at org.gradle.tooling.internal.consumer.DefaultAsyncConnection$2.run(DefaultAsyncConnection.java:53)
at org.gradle.tooling.internal.consumer.DefaultAsyncConnection$2.run(DefaultAsyncConnection.java:51)
at org.gradle.tooling.internal.consumer.DefaultAsyncConnection$3.run(DefaultAsyncConnection.java:71)
... 4 more

I am also unable to connect to the Gradle daemon, either from the command line or from STS 2.8/2.9. I'm on WinXP 32bit, with Sun/Oracle JDK 1.6.0_31.

C:\>gradle --daemon --stacktrace
Note: the Gradle build daemon is an experimental feature.
As such, you may experience unexpected build failures. You may need to occasiona
lly stop the daemon.

FAILURE: Build failed with an exception.

• What went wrong:
  Timeout waiting to connect to Gradle daemon.

• Try:
  Run with --info or --debug option to get more log output.

• Exception is:
  org.gradle.api.GradleException: Timeout waiting to connect to Gradle daemon.
  at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:109)
  at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:103)
  at org.gradle.launcher.cli.DaemonBuildAction.run(DaemonBuildAction.java:49)
  at org.gradle.launcher.cli.CommandLineActionFactory$ActionAdapter.execute(CommandLineActionFactory.java:214)
  at org.gradle.launcher.cli.CommandLineActionFactory$ActionAdapter.execute(CommandLineActionFactory.java:206)
  at org.gradle.launcher.exec.ExceptionReportingAction.execute(ExceptionReportingAction.java:32)
  at org.gradle.launcher.exec.ExceptionReportingAction.execute(ExceptionReportingAction.java:21)
  at org.gradle.launcher.cli.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:238)
  at org.gradle.launcher.cli.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:222)
  at org.gradle.launcher.Main.doAction(Main.java:48)
  at org.gradle.launcher.exec.EntryPoint$1.execute(EntryPoint.java:53)
  at org.gradle.launcher.exec.EntryPoint$1.execute(EntryPoint.java:51)
  at org.gradle.launcher.exec.Execution.execute(Execution.java:28)
  at org.gradle.launcher.exec.EntryPoint.run(EntryPoint.java:39)
  at org.gradle.launcher.Main.main(Main.java:39)
  at org.gradle.launcher.ProcessBootstrap.runNoExit(ProcessBootstrap.java:51)
  at org.gradle.launcher.ProcessBootstrap.run(ProcessBootstrap.java:33)
  at org.gradle.launcher.GradleMain.main(GradleMain.java:24)

@James, which version of Gradle are you using (you can run gradle -v to get the details)? Also, could you try with the recent 1.0-milestone-9 snapshot (see http://gradle.org/release-candidate)? There have been a bunch of fixes in this area.

Also, can you run with --debug ?

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.