[
https://issues.apache.org/jira/browse/OAK-11242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895608#comment-17895608
]
Julian Reschke commented on OAK-11242:
--------------------------------------
[~ahanikel] - I assume this can be set to "resolved"?
> 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
> Priority: Major
>
> 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)
