[GRADLE-2020] Locked cache directory Created: 31/Dec/11  Updated: 04/Jan/13  Resolved: 31/Dec/11

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-6
Fix Version/s: 1.0-milestone-7

Type: Bug
Reporter: Benjamin Muschko Assignee: Adam Murdoch
Resolution: Fixed Votes: 0

Issue Links:
Duplicated by GRADLE-1801 Could not open cache directory ... ta... Resolved


When trying to run two tasks of the same Gradle project at the same time Gradle reports a locked cache directory. Is there a specific reason for it? In my use case I'd like to have a running instance of a servlet container in one shell and recompile sources in another shell to replace the compiled class in the ClassLoader via JRebel. This is impossible at the moment.

FAILURE: Build failed with an exception.

* What went wrong:
Could not open cache directory /Users/benjamin/dev/opensource/gradle-tomcat/.gradle/1.0-milestone-6/taskArtifacts.
Cause: Timeout waiting to lock cache directory /Users/benjamin/dev/opensource/gradle-tomcat/.gradle/1.0-milestone-6/taskArtifacts. It is currently in use by another Gradle instance.
Owner PID: 5559
Our PID: 5550
Owner Operation: 
Our operation: 
Lock file: /Users/benjamin/dev/opensource/gradle-tomcat/.gradle/1.0-milestone-6/taskArtifacts/cache.properties.lock

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