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

Nicolas Filotto edited comment on CAMEL-18582 at 10/10/22 10:41 AM:
--------------------------------------------------------------------

By default, {{SocketTimeoutException}} as a subclass of 
{{InterruptedIOException}} is part of the non-retryable classes which is the 
reason why no retries are made, so we need to redefine the non-retryable 
classes without {{InterruptedIOException}} to make sure that it will retry in 
case of {{Read timed out}}

The PR to remove SocketTimeoutException from non retryable classes 
[https://github.com/apache/camel/pull/8497]

 

During the last build, we can see[ in the log 
file|https://github.com/apache/camel/actions/runs/3209749409/jobs/5261980216] 
that several `read timed out`s occurred but the build still passed, so it 
should be good now


was (Author: JIRAUSER285918):
By default, {{SocketTimeoutException}} as a subclass of 
{{InterruptedIOException}} is part of the non-retryable classes which is the 
reason why no retries are made, so we need to redefine the non-retryable 
classes without {{InterruptedIOException}} to make sure that it will retry in 
case of {{Read timed out}}

{{}}

The PR to remove SocketTimeoutException from non retryable classes 
[https://github.com/apache/camel/pull/8497]

 

During the last build, we can see[ in the log 
file|https://github.com/apache/camel/actions/runs/3209749409/jobs/5261980216] 
that several `read timed out`s occurred but the build still passed, so it 
should be good now

> 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)

Reply via email to