Should I Close JDBC Connections from a Connection Pool?

Closing JDBC Connections in Pool

Question 1: Closing Pooled Connections

When utilizing a JDBC connection pool, it is crucial to close the pooled connection after usage. Contrary to popular belief, this does not undermine the purpose of pooling. Instead, it allows the pool to reclaim the underlying actual connection and make it available for reuse.

Question 2: Standard Connection Retrieval Method

The provided getConnection method attempts to retrieve a connection from the pool. However, it resorts to the traditional DriverManager approach if the pool lookup fails. This design flaw makes it difficult to determine which method is employed at runtime. To ensure proper behavior and resource management, refrain from using such a method and instead opt for a consistent approach by initializing the DataSource once during application startup.

Closing Connections from Other Methods

It is essential to close connections obtained from any method, regardless of its implementation details. By employing a try-with-resources statement or explicitly closing the resources in a finally block, you ensure proper cleanup and return of resources to the pool.

See Also:

• [Is it safe to use a static java.sql.Connection instance in a multithreaded system?](https://stackoverflow.com/questions/3914092/is-it-safe-to-use-a-static-javasql-connection-instance-in-a-multithreaded-sy)
• [Am I Using JDBC Connection Pooling?](https://stackoverflow.com/questions/2641371/am-i-using-jdbc-connection-pooling)

The above is the detailed content of Should I Close JDBC Connections from a Connection Pool?. For more information, please follow other related articles on the PHP Chinese website!