Is a finally block the correct location to close a database connection?

Question

Possible Duplicate:
Is java.sql.Connection thread safe?

I have gone through some tutorials.
They said to close the database connection through finally block.
But I have a question on my mind:

Think about a scenario where two threads are actively reading on one connection and one thread finishes his work and closes the connection. So what happens to the other?

Is the second thread able to complete his task?

Please let me know if my question is not valid and please let me know the best solution.

You should not share a single `java.sql.Connection` between two threads at the same time. — erickson, Nov 15 '11 at 08:01
@erickson that ought to be an answer so it can get upvoted and accepted — Will, Nov 15 '11 at 08:02

score 5 · Answer 1 · answered Nov 15 '11 at 08:06

Yes, a finally block is the correct way to close a Connection and other JDBC resources.

You should avoid sharing such objects between threads; while they are probably thread-safe, they are not intended to be used in this way. One JDBC specification says, "In practice we expect that most of the JDBC objects will only be accessed in a single threaded way."

If you have multiple threads using the same database, create a pool of connections, and allow each thread exclusive access to a Connection and its subsidiary resources.

Is a finally block the correct location to close a database connection?

1 Answers1