Answer.

The try-with-resources mechanism was introduced in Java 7 for automatic resource management, such as input-output streams or database connections. It simplifies resource handling and minimizes leakage errors.

Background:

Before Java 7, resources had to be closed manually in the finally block, leading to code duplication and errors. Try-with-resources automated this process, making the code cleaner and safer.

Problem:

If a resource was not explicitly closed, a leak could occur (for example, a file handle or a database connection not being released). In the old scheme, developers often forgot to call close() in the finally block, especially in cases of multiple exceptions.

Solution:

Use try-with-resources everywhere resources implement the AutoCloseable interface.

Example usage:

try (BufferedReader reader = new BufferedReader(new FileReader("file.txt"))) {
    String line = reader.readLine();
    // ...
} catch (IOException e) {
    e.printStackTrace();
}

When exiting the try block, close() will be called automatically, ensuring proper resource release.

Key features:

Uses the AutoCloseable interface
Automatically releases resources on any exit from the block
Ensures code cleanliness and compactness

Tricky questions.

Can you use try-with-resources with multiple resources?

Yes, you can declare multiple resources in one line separated by semicolons:

try (
    InputStream in = new FileInputStream("a.txt");
    OutputStream out = new FileOutputStream("b.txt")
) {
    // ...
}

Is it mandatory to catch exceptions in try-with-resources?

No. You can omit catch if the method declares throwing an exception or handling is not required, but catch is often needed for proper diagnosis.

Can you use variables declared outside of try() as resources for try-with-resources?

No, resources must be declared within the try parentheses; otherwise, auto-closing will not work.

Common mistakes and anti-patterns

Not closing resources in old try-catch constructions
Trying to use try-with-resources with objects that do not implement AutoCloseable
Declaring resources outside of try(), losing auto-closing

Real-life example

Negative case

The code opens FileInputStream without try-with-resources, and the developer forgets to close the stream or only closes it when there are no errors. In case of an exception, the stream remains open.

Pros:

Classic, familiar scheme

Cons:

Resource leaks
Complex and repetitive error handling code

Positive case

Try-with-resources is used, the resource is declared right inside the try parentheses, and release is always guaranteed.