[jira] [Comment Edited] (MNG-7868) "Could not acquire lock(s)" error in concurrent maven builds

["Joe Witt (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780638#comment-17780638 ] 

Joe Witt edited comment on MNG-7868 at 10/28/23 5:22 PM:
---------------------------------------------------------

Hello.  We in Apache NiFi run into this very same issue quite frequently and we certainly have hot artifacts used all over the place and we very much are multi-module.  I see this on OSX (quite often).  And I'm on Apache Maven 3.9.5 as well

FWIW I just added 

-Daether.connector.basic.threads=8 -Daether.metadataResolver.threads=8
    -Daether.syncContext.named.time=120

To my normal build string and indeed this time it ran clean.

I will say this issue happens sometimes more than others.  I've gone days without seeing it then today it happened two builds in a row.

Thanks


was (Author: joewitt):
Hello.  We in Apache NiFi run into this very same issue quite frequently and we certainly have hot artifacts used all over the place and we very much are multi-module.  I see this on OSX (quite often).  

FWIW I just added 

-Daether.connector.basic.threads=8 -Daether.metadataResolver.threads=8
    -Daether.syncContext.named.time=120

To my normal build string and indeed this time it ran clean.

I will say this issue happens sometimes more than others.  I've gone days without seeing it then today it happened two builds in a row.

Thanks

> "Could not acquire lock(s)" error in concurrent maven builds
> ------------------------------------------------------------
>
>                 Key: MNG-7868
>                 URL: https://issues.apache.org/jira/browse/MNG-7868
>             Project: Maven
>          Issue Type: Bug
>         Environment: windows, maven 3.9.4
>            Reporter: Jörg Hohwiller
>            Priority: Major
>
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install) on project foo.bar: Execution default-install of goal org.apache.maven.plugins:maven-install-plugin:3.1.1:install failed: Could not acquire lock(s) -> [Help 1]
> {code}
> I am using maven 3.9.4 on windows:
> {code}
> $ mvn -v
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: D:\projects\test\software\mvn
> Java version: 17.0.5, vendor: Eclipse Adoptium, runtime: D:\projects\test\software\java
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> {code}
> I searched for this bug and found issues like MRESOLVER-332 that first look identical or similar but do not really seem to be related so I decided to create this issue.
> For this bug I made the following observations:
> * it only happens with concurrent builds: {{mvn -T ...}}
> * is seems to be windows related (at least mainly happens on windows)
> * it is in-deterministic and is not so easy to create an isolated and simple project and a reproducible scenario that always results in this error. However, I get this very often in my current project with many modules (500+).
> * it is not specific to the maven-install-plugin and also happens from other spots in maven:
> I also got this stacktrace:
> {code}
> Suppressed: java.lang.IllegalStateException: Attempt 1: Could not acquire write lock for 'C:\Users\hohwille\.m2\repository\.locks\artifact~com.caucho~com.springsource.com.caucho~3.2.1.lock' in 30 SECONDS
>         at org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapter$AdaptedLockSyncContext.acquire (NamedLockFactoryAdapter.java:202)
>         at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:271)
>         at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:259)
>         at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies (DefaultRepositorySystem.java:352)
> {code}
> See also this related discussion:
> https://github.com/apache/maven-mvnd/issues/836#issuecomment-1702488377



--
This message was sent by Atlassian Jira
(v8.20.10#820010)