Gradle tasks timeout after build.gradle modified while jetty is running

[auriusbendikas]

I am using jetty plugin to test my work. I have noticed that if I modify build.gradle while jetty is started (by gradle), than all other task executions timeout with this exeption:

Timeout waiting to lock buildscript class cache for build file '{project}/build.gradle' ({gradle_home}/caches/1.11/scripts/build_307eri5rn2tng6h3pvh4svs119/ProjectScript/buildscript). It is currently in use by another Gradle instance.
Owner PID: unknown
Our PID: 7053
Owner Operation: unknown
Our operation: Initialize cache
Lock file: {gradle_home}/caches/1.11/scripts/build_307eri5rn2tng6h3pvh4svs119/ProjectScript/buildscript/cache.properties.lock
Could not execute build using Gradle installation '{1.11-gradle-install-location}/gradle'.

The only way to get out of this situation is to manually kill gradle daemons.

[yanglichuan]

Error:Timeout waiting to lock cp_proj class cache for build file 'E:\BoyMagicSeed0120\BoyMagicSeed0120\build.gradle' (C:\Users\Administrator.gradle\caches\2.10\scripts\build_59zgeoad80d0p03j4ho75l4aj\cp_proj). It is currently in use by another Gradle instance.
Owner PID: unknown
Our PID: 18540
Owner Operation: unknown
Our operation: Initialize cache
Lock file: C:\Users\Administrator.gradle\caches\2.10\scripts\build_59zgeoad80d0p03j4ho75l4aj\cp_proj\cache.properties.lock

[Giszmo]

For what it's worth, I ran into this error without any jetty as far as I can see. AndroidStudio froze while trying to sync the build.gradle. Can't reproduce but it's almost certainly not a jetty issue.