Closing JDBC Connections in Pool

by

When using Connection Pool, should one close the Connection at the end? If so, isn’t the purpose of pooling lost? And if not, how does the DataSource know when a particular instance of Connection is freed up and can be reused? I am a little confused on this one, any pointers appreciated.

Yes, certainly you need to close the pooled connection as well. It’s actually a wrapper around the actual connection. It wil under the covers release the actual connection back to the pool. It’s further up to the pool to decide whether the actual connection will actually be closed or be reused for a new getConnection() call. So, regardless of whether you’re using a connection pool or not, you should always close all the JDBC resources in reversed order in the finally block of the try block where you’ve acquired them. In Java 7 this can be further simplified by using try-with-resources statement.

Is the following method anything close to standard? Looks like an attempt to get a connection from the pool, and if DataSource cannot be established, use the old fashioned DriverManager. We are not even sure which part is getting executed at runtime. Repeating the question above, should one close the Connection coming out of such a method?

The example is pretty scary. You just need to lookup/initialize the DataSource only once during application’s startup in some constructor / initialization of an applicationwide DB config class. Then just call getConnection() on the one and same datasource throughout the rest of application’s lifetime. No need for synchronization nor nullchecks.

See also:

More Related Contents:

  1. JDBC MySql connection pooling practices to avoid exhausted connection pool
  2. SQL syntax error in "insert into 'keys'(a,b,c,d,e) values(?,?,?,?,?)" [closed]
  3. Hours and seconds are lost when storing a date in the database [closed]
  4. com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
  5. Solving a “communications link failure” with JDBC and MySQL [duplicate]
  6. Multiple queries executed in java in single statement
  7. How to establish a connection pool in JDBC?
  8. Connection pooling options with JDBC: DBCP vs C3P0 [closed]
  9. Java: Insert multiple rows into MySQL with PreparedStatement
  10. ClassCastException: java.math.BigInteger cannot be cast to java.lang.Long on connect to MySQL
  11. Cannot issue data manipulation statements with executeQuery()
  12. Handling MySQL datetimes and timestamps in Java
  13. No suitable driver found for ‘jdbc:mysql://localhost:3306/mysql [duplicate]
  14. com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:Communications link failure [duplicate]
  15. “Loading class com.mysql.jdbc.Driver … is deprecated” message
  16. How to configure Tomcat to connect with MySQL
  17. Retrieve an Image stored as BLOB on a MYSQL DB
  18. Can I execute multiple queries separated by semicolon with MySQL Connector/J? [duplicate]
  19. runtime error: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
  20. mysql prepared statement error: MySQLSyntaxErrorException
  21. ‘0000-00-00 00:00:00’ can not be represented as java.sql.Timestamp error
  22. SQL Error: 0, SQLState: 08S01 Communications link failure [duplicate]
  23. MySQL connector error “The server time zone value Central European Time” [duplicate]
  24. How to correctly write UTF-8 strings into MySQL through JDBC interface
  25. Glassfish Admin Console throws java.lang.IllegalStateException when creating JDBC Pool
  26. java.sql.SQLException: Before start of result set [duplicate]
  27. Stumped SQL Exception for JDBC
  28. A datetime equivalent in java.sql ? (is there a java.sql.datetime ?)
  29. How to connect to a remote MySQL database with Java?
  30. A persistent connection with JDBC to MySQL

Leave a Comment