Try Without Catch in Java

Yes, you can absolutely have a try without a catch. The actual rule in Java is that a try block has to be followed by at least one of three things: one or more catch blocks, a finally block, or, since Java 7, it can be a try-with-resources statement. What you can't have is a try with nothing after it — a bare try block on its own is a compile error. So the form that surprises freshers is try-finally with no catch in between. That pattern is genuinely useful, and the use case is when you want structured cleanup but you don't actually want to handle the exception at this level. A classic example is acquiring a lock: you lock, then in the try you do your work, and in the finally you unlock. There's no catch, so if the work throws, the finally still runs and releases the lock, and then the exception propagates up to whoever called you. That's the key point — the finally doesn't consume or swallow the exception, it just guarantees the cleanup happens before the exception leaves the method. The caller, which is usually in a better position to decide what to do, still receives the error. A mistake I'd warn against is adding an empty catch block just to make the code compile, because that silently swallows the exception and hides bugs. If all you need is cleanup, use try-finally rather than an empty catch. And these days, for things that implement AutoCloseable like streams or J D B C connections, try-with-resources is even cleaner because it closes the resource for you automatically.