Using gradle on my laptop (which is rebooted about one or two times a week, rest is just suspend-to-disk) I have gradle failures that seem to be related to network changes.
Resuming the machine and connect to a different WLAN AP or ethernet I get failures like this:
FAILURE: Build failed with an exception. * What went wrong: Unable to start the daemon process. This problem might be caused by incorrect configuration of the daemon. For example, an unrecognized jvm option is used. Please refer to the user guide chapter on the daemon at http://gradle.org/docs/1.6/userguide/gradle_daemon.html Please read below process output to find out more: ----------------------- Error occurred during initialization of VM Could not reserve enough space for object heap Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.
gradle --stop says that no daemons are running and I don’t see any java processes. Now when I change the access point gradle runs. Changing the access point back (to the failing) one: gradle works. I also deleted everything under .gradle, which has no effect.
Are there any other locks or system wide objects that gradle creates ? Or is this some kind of JVM cache (but eclipse, ant etc. work without problems) ?