If a finally clause is specified, irrespective of whether the try or catch block executes to completion or not, the finally block is executed. Consequently statements that abruptly exit from cause the finally block may cause to terminate abruptly may can mask of any thrown exceptions to be masked. Consequently, keywords like return, break, continue and throw should never be used within a finally block.
...
Here, the finally block completes abruptly since because a return statement occurs within it. As a result, when the IllegalStateException is thrown, it does not propagate all the way up through the call stack. This is due to because of the abrupt termination of the finally block that suppresses any useful exception information from being displayed by overriding the exception thrown in the try block by overriding it with its own message. Note that even if the try block returns some value, the finally block is executed.
...
This compliant solution removes the return statement from the finally block. Any return statements must occur after this block. In If this exampleis adopted, the compiler will throw throws an error as the return statement is unreachable due to because of the explicit, unavoidable throwing of IllegalStateException. If the exception is thrown conditionally, the return statement can be used without any compilation errors.
...
Risk Assessment
Exiting abruptly from a finally block may lead to cause the masking of thrown exceptions.
...