Never use return
, break
, continue
, or throw
statements within a finally
block. When program execution enters a try
block that has a finally
block, the finally
block always executes regardless of whether the try
block (or any associated catch
blocks) executes to normal completion. Statements that cause the finally
block to complete abruptly also cause the try
block to complete abruptly and consequently suppress any exception thrown from the try
or catch
blocks. According to The Java Language Specification, §14.20.2, "Execution of try-finally
and try-catch-finally
" [JLS 2015]:
If execution of the
try
block completes abruptly for any other reasonR
, then thefinally
block is executed. Then there is a choice:
- If the
finally
block completes normally, then thetry
statement completes abruptly for reasonR
.- If the
finally
block completes abruptly for reasonS
, then thetry
statement completes abruptly for reasonS
(and reasonR
is discarded).
Noncompliant Code Example
In this noncompliant code example, the finally
block completes abruptly because of a return
statement in the block:
class TryFinally { private static boolean doLogic() { try { throw new IllegalStateException(); } finally { System.out.println("logic done"); return true; } } }
The IllegalStateException
is suppressed by the abrupt completion of the finally
block caused by the return
statement.
Compliant Solution
This compliant solution removes the return
statement from the finally
block:
class TryFinally { private static boolean doLogic() { try { throw new IllegalStateException(); } finally { System.out.println("logic done"); } // Any return statements must go here; // applicable only when exception is thrown conditionally } }
Exceptions
ERRO4-J-EX0: Control flow statements whose destination is within the finally
block are perfectly acceptable. For example, the following code does not violate this rule because the break
statement exits within the while
loop but not within the finally
block:
class TryFinally { private static boolean doLogic() { try { throw new IllegalStateException(); } finally { int c; try { while ((c = input.read()) != -1) { if (c > 128) { break; } } } catch (IOException x) { // Forward to handler } System.out.println("logic done"); } // Any return statements must go here; applicable only when exception is thrown conditionally } }
Risk Assessment
Abrupt completion of a finally
block masks any exceptions thrown inside the associated try
and catch
blocks.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
ERR04-J | Low | Probable | Medium | P4 | L3 |
Automated Detection
Tool | Version | Checker | Description |
---|---|---|---|
Coverity | 7.5 | PW.ABNORMAL_TERMINATION_ OF_FINALLY_BLOCK | Implemented |
Parasoft Jtest | 2024.1 | CERT.ERR04.ARCF CERT.ERR04.ATSF | Avoid using 'return's inside 'finally blocks if thare are other 'return's inside the try-catch block Do not exit "finally" blocks abruptly |
PVS-Studio | 7.33 | V6051 | |
SonarQube | 9.9 | S1143 | Jump statements should not occur in "finally" blocks |
Related Guidelines
Bibliography
Puzzle 36. Indecision | |
Section 8.2, "Managing Exceptions, The Vanishing Exception" | |
[JLS 2015] |
6 Comments
Robert Seacord (Manager)
Not sure what this statement in first NCE is trying to say:
Robert Seacord (Manager)
OK, I think I fixed this so I moved this rule to tech-edit status.
Robert Seacord (Manager)
While true, the following text from the CS seems irrelevant to me and should probably be removed:
David Svoboda
agreed, removed
Dhruv Mohindra
David Svoboda
Added an exception explaining this
Done
Agreed. Changed the println text.