[
https://issues.apache.org/jira/browse/STORM-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
LoggingResearch updated STORM-3938:
-----------------------------------
External issue URL: https://github.com/apache/storm/pull/3554
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
was:
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.
> Unhandled InterruptedException in Supervisor's close() method
> -------------------------------------------------------------
>
> Key: STORM-3938
> URL: https://issues.apache.org/jira/browse/STORM-3938
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-server
> Affects Versions: 2.4.0
> Reporter: LoggingResearch
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
