[
https://issues.apache.org/jira/browse/CAMEL-18582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614097#comment-17614097
]
Nicolas Filotto commented on CAMEL-18582:
-----------------------------------------
After a deeper analysis, it appears that the build failures are indirectly due
to errors of type {{I/O exception (java.net.SocketException) caught when
processing request to \{s}->https://repo.maven.apache.org:443: Connection timed
out (Read failed)}} which has consequences to keep the lock on the artifacts
for more than 15 minutes such that the build ends up with a lock issue since
the lock timeout is only 5 minutes.
The PR to update the timeouts involved https://github.com/apache/camel/pull/8488
> Prevent build failures due to write lock issues
> -----------------------------------------------
>
> Key: CAMEL-18582
> URL: https://issues.apache.org/jira/browse/CAMEL-18582
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Nicolas Filotto
> Assignee: Nicolas Filotto
> Priority: Major
>
> The build regularly fails with an error of type:
>
> {{2022-10-04T08:27:32.6309180Z [ERROR] Could not acquire write lock for
> '/home/runner/.m2/repository/.locks/jakarta.activation~jakarta.activation-api~1.2.2.resolverlock'
> 2022-10-04T08:27:32.6313534Z [ERROR] Camel :: Management: Could not acquire
> write lock for
> '/home/runner/.m2/repository/.locks/jakarta.activation~jakarta.activation-api~1.2.2.resolverlock'}}
>
> The goal of this task is to investigate the issue and find a way to fix it or
> at least find a workaround.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
