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 2025/02/13 10:17:00 UTC
[jira] [Created] (OAK-11480) AzureRepositoryLock: NPE in refresh thread
Joerg Hoh created OAK-11480:
-------------------------------
Summary: AzureRepositoryLock: NPE in refresh thread
Key: OAK-11480
URL: https://issues.apache.org/jira/browse/OAK-11480
Project: Jackrabbit Oak
Issue Type: Bug
Components: segment-azure
Affects Versions: 1.72.0
Reporter: Joerg Hoh
I came across a NPE in the AzureRepositoryLock refreshing logic, which terminates this thread and renders the repository unusable, so eventually the service needs to be terminated.
Fixing this NPE would be highly appreciated.
{noformat}
[AzureRepositoryLock-Refresher] org.apache.jackrabbit.oak.segment.azure.AzureRepositoryLock Unexpected error in the lease renewal loop, trying to recover java.lang.NullPointerException: null
at java.base/java.util.Objects.requireNonNull(Objects.java:221)
at java.base/java.util.ImmutableCollections$SetN.contains(ImmutableCollections.java:601)
at org.apache.jackrabbit.oak.segment.azure.AzureRepositoryLock.refreshLease(AzureRepositoryLock.java:162) [org.apache.jackrabbit.oak-segment-azure:1.72.0]
at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
I see this bug already reported in https://github.com/Azure/azure-sdk-for-java/issues/38646, and the recommendation is to update the Azure library to a more recent one.
I have found OAK-11267 for it, but I am not sure about the progress there, so I recommend to add here a check to avoid this NPE until the SDK version was upgraded
--
This message was sent by Atlassian Jira
(v8.20.10#820010)