Try With Resources vs Try-Catch [duplicate]

by

The main point of try-with-resources is to make sure resources are closed reliably without possibly losing information.

When you don’t use try-with-resources there’s a potential pitfall called exception-masking. When code in a try block throws an exception, and the close method in the finally also throws an exception, the exception thrown by the try block gets lost and the exception thrown in the finally gets propagated. This is usually unfortunate, since the exception thrown on close is something unhelpful while the informative one is the one thrown from within the try block. (So instead of seeing the SQLException that tells you which referential integrity constraint was violated, you’re shown something like BrokenPipeException where closing the resource failed.)

This exception-masking is an annoying problem that try-with-resources prevents from happening.

As part of making sure exception-masking wouldn’t lose important exception information, when try-with-resources was developed they had to decide what to do with the exceptions thrown from the close method.

With try-with-resources, if the try block throws an exception and the close method also throws an exception, then the exception from the close block gets tacked on to the original exception:

… there are situations where two independent exceptions can be thrown in sibling code blocks, in particular in the try block of a try-with-resources statement and the compiler-generated finally block which closes the resource. In these situations, only one of the thrown exceptions can be propagated. In the try-with-resources statement, when there are two such exceptions, the exception originating from the try block is propagated and the exception from the finally block is added to the list of exceptions suppressed by the exception from the try block. As an exception unwinds the stack, it can accumulate multiple suppressed exceptions.

On the other hand if your code completes normally but the resource you’re using throws an exception on close, that exception (which would get suppressed if the code in the try block threw anything) gets thrown. That means that if you have some JDBC code where a ResultSet or PreparedStatement is closed by try-with-resources, an exception resulting from some infrastructure glitch when a JDBC object gets closed can be thrown and can rollback an operation that otherwise would have completed successfully.

Without try-with-resources whether the close method exception gets thrown is up to the application code. If it gets thrown in a finally block when the try block throws an exception, the exception from the finally block will mask the other exception. But the developer has the option of catching the exception thrown on close and not propagating it.

More Related Contents:

  1. Try-with-resources equivalent in Java 1.6
  2. NumberFormatException not wrking java
  3. Catching java.lang.OutOfMemoryError?
  4. Is it expensive to use try-catch blocks even if an exception is never thrown?
  5. How do you implement a re-try-catch?
  6. Program freezes during Thread.sleep() and with Timer
  7. Why does a Try/Catch block create new variable scope?
  8. Problem with “scopes” of variables in try catch blocks in Java
  9. Try-catch-finally-return clarification [duplicate]
  10. try with resources introduce unreachable bytecode
  11. Correct idiom for managing multiple chained resources in try-with-resources block?
  12. Java if vs. try/catch overhead
  13. Java try/catch/finally best practices while acquiring/closing resources
  14. Java io ugly try-finally block
  15. EOFException – how to handle?
  16. Throws or try-catch
  17. What is a suppressed exception?
  18. Java Try Catch Finally blocks without Catch
  19. Java try/catch performance, is it recommended to keep what is inside the try clause to a minimum?
  20. Try-with-resources and return statements in java
  21. Should try…catch go inside or outside a loop?
  22. Close multiple resources with AutoCloseable (try-with-resources)
  23. How can I catch Event Dispatch Thread (EDT) exceptions?
  24. What are the circumstances under which a finally {} block will NOT execute?
  25. Catching an exception that is nested into another exception
  26. Java 7 Automatic Resource Management JDBC (try-with-resources statement)
  27. Why is declaration required in Java’s try-with-resource
  28. Java InputMismatchException
  29. How can I catch all exceptions thrown through reading / writing a file?
  30. try-catch for division by zero

Leave a Comment