You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2024/11/14 07:45:01 UTC

[jira] [Closed] (OAK-11242) AzureRepositoryLock: Thread should not die silently on any kind of error

     [ https://issues.apache.org/jira/browse/OAK-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joerg Hoh closed OAK-11242.
---------------------------

> AzureRepositoryLock: Thread should not die silently on any kind of error
> ------------------------------------------------------------------------
>
>                 Key: OAK-11242
>                 URL: https://issues.apache.org/jira/browse/OAK-11242
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-azure
>    Affects Versions: 1.70.0
>            Reporter: Axel Hanikel
>            Assignee: Axel Hanikel
>            Priority: Major
>             Fix For: 1.72.0
>
>
> This is a follow-up to OAK-11069: Apparently the refresher thread still dies without a trace. I'm therefore assuming some java.lang.Error occurs, which is hidden behind the executor. An approach could be to avoid the executor in favour of creating the thread ourselves, and catching all Throwables to make sure we handle them. We leave fatal errors such as OOME to pop up in other parts of the code.



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