[
https://issues.apache.org/jira/browse/CAMEL-18582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612957#comment-17612957
]
Nicolas Filotto edited comment on CAMEL-18582 at 10/5/22 11:20 AM:
-------------------------------------------------------------------
It appears that the problem still happens with the
LocalReadWriteLockNamedLockFactory so the lock timeout is increased to 5
minutes and a thread dump is automatically generated in case of a lock issue to
be able to investigate deeper if it still occurs.
was (Author: JIRAUSER285918):
It appears that the problem still happens with the
LocalReadWriteLockNamedLockFactory so the lock timeout is increased to 5
minutes and a thread dump is automatically generated in case of a lock issue to
be able to investigate deeper if it still occures.
> 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)
