Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-11242

AzureRepositoryLock: Thread should not die silently on any kind of error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.70.0
    • 1.72.0
    • segment-azure
    • None

    Description

      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.

      Attachments

        Issue Links

          split from

          Bug - A problem which impairs or prevents the functions of the product. OAK-11069 AzureRepositoryLock: Thread should not die silently on exceptions other than StorageException

          • Major - Major loss of function.
          • Closed
          links to

          Web Link GitHub Pull Request #1838

          Activity

            People

              ahanikel Axel Hanikel
              ahanikel Axel Hanikel
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: