Uploaded image for project: 'Apache Storm'
  1. Apache Storm
  2. STORM-3938

Unhandled InterruptedException in Supervisor's close() method

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Blocker
    • Resolution: Won't Fix
    • 2.4.0
    • None
    • storm-server
    • None

    Description

      In the Supervisor class's close() method, we are attempting to close the asyncLocalizer object which can throw an InterruptedException. However, currently, the InterruptedException thrown by asyncLocalizer.close() is not being caught or logged. This is an issue because InterruptedException is a more specific exception that might need to be handled separately from the general Exception catch block.

      This can lead to a situation where if an InterruptedException is thrown, we will not have any log information about it, making it difficult to debug the issue.

      Proposed solution:

      Add a separate catch block for InterruptedException before the general Exception catch block to handle and log the InterruptedException properly.

      https://github.com/apache/storm/pull/3554

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rzo1 Richard Zowalla
            loggingresearch LoggingResearch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h
                1h

                Slack

                  Issue deployment