findbugs异常（1）：Exception is caught when Exception is not thrown

最新推荐文章于 2022-12-23 10:33:58 发布

原创最新推荐文章于 2022-12-23 10:33:58 发布 · 8.8k 阅读

4 ·

CC 4.0 BY-SA版权

文章标签：

#bug

Exception 专栏收录该内容

20 篇文章

订阅专栏

本文探讨了Java中异常处理的常见误区与最佳实践，强调了避免过泛地捕获异常的重要性，并提供了具体的代码示例说明如何正确处理不同类型的异常。

1. findbugs官方解释：

Exception is caught when Exception is not thrown
This method uses a try-catch block that catches Exception objects, but Exception is not thrown within the try block, and RuntimeException is not explicitly caught. It is a common bug pattern to say try { ... } catch (Exception e) { something } as a shorthand for catching a number of types of exception each of whose catch blocks is identical, but this construct also accidentally catches RuntimeException as well, masking potential bugs.
A better approach is to either explicitly catch the specific exceptions that are thrown, or to explicitly catch RuntimeException exception, rethrow it, and then catch all non-Runtime Exceptions, as shown below:
try {
...
} catch (RuntimeException e) {
throw e;
} catch (Exception e) {
... deal with all non-runtime exceptions ...
}

2. 一般人都会这样写代码：

  try{
　　　　//
　　}
　　catch(Exception ex){
　　　　//
　　}

3. 这样很省事，但是JAVA规范中并不推荐这样做，这样是属于“过泛地捕获异常”，因为try{}中可能出现的异常种类有很多，上面的做法不利于分别处理各种异常，建议根据业务需求，分别捕获需要特别处理的异常，例子如下：

  try{
　　　　//
　　}
　　catch(SQLException ex){
　　　　//
　　}
　　catch(IOException ex){
　　　　//
　　}
　　catch(Exception ex){
　　　　//
　　}

4. 捕获的异常一定要抛出，并打印日志。