Try Catch Finally Execution Order in Java

Direct Answer

The try block runs first. If it throws, control jumps to the matching catch (skipping the rest of try); if nothing throws, catch is skipped entirely. The finally block runs last in both cases — after try (success) or after catch (failure) — and even runs before a return. So the order is try → (catch only on error) → finally normally.

Code Example

public class OrderFlow {
    String load(boolean fail) {
        try {
            System.out.println("1: try start");
            if (fail) throw new RuntimeException("boom");
            System.out.println("2: try end");   // skipped if fail
            return "ok";
        } catch (RuntimeException e) {
            System.out.println("3: catch");      // only when fail
            return "recovered";
        } finally {
            System.out.println("4: finally");    // ALWAYS
        }
    }
}
// load(false) prints 1,2,4  -> returns "ok"
// load(true)  prints 1,3,4  -> returns "recovered"

Common Mistakes & Pitfalls

• Expecting the rest of try to run after a throw: control leaves that path immediately.
• Thinking finally requires a matching catch: finally normally runs while the statement exits whether or not a catch handled the failure.
• Calling finally an unconditional guarantee: termination or code that never exits the protected region can prevent cleanup.
• Returning or throwing from finally: it can replace an earlier return or exception.
• Using finally for closeable resources: try-with-resources applies safer structured closing rules.