Should I Close JDBC Connections Even When Using a Connection Pool?

Closing JDBC Connections in Pooling Configuration

When using a connection pool, it is crucial to close the connection at the end of its usage, despite the common misconception that it negates the purpose of pooling. By closing the connection, you effectively return it to the pool. This allows the pool to manage its resources and decide whether to close the actual connection or reuse it for subsequent getConnection() calls.

However, in the provided code snippet, you attempt to switch between a pooled connection and a direct connection from the DriverManager. This practice is strongly discouraged. Instead, establish a single DataSource during application initialization and rely solely on it to retrieve connections. By doing so, you eliminate the need for synchronization, null checks, and uncertainty about which connection method is invoked at runtime.

Closing Connections Derived from Hybrid Methods

Yes, it is necessary to close the connection returned by the hybrid method you presented. Regardless of the method used to acquire the connection, the general principle of closing JDBC resources in reversed order remains applicable. This practice ensures proper resource cleanup and prevents resource exhaustion.

Standard Practice for Connection Acquisition

In general, the preferred approach for acquiring a JDBC connection involves:

1. Initializing a DataSource once during application startup.
2. Repeatedly calling getConnection() on the DataSource throughout the application's lifetime.

This simple and straightforward approach eliminates the complexities and uncertainties associated with hybrid connection acquisition methods.

Additional Resources

• Is it safe to use a static java.sql.Connection instance in a multithreaded system?
• Am I Using JDBC Connection Pooling?

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