Do you need to close the connection you get from jdbc connection pool?

Question

Suppose I have the following code

DataSource source = (DataSource) (new InitialContext()).lookup("jdbc/myName"); 
Connection connnection = source.getConnection() 

//use the connection to do some database operations...

at the end, should I still call

connection.close() to release the resource?

If the connection is from a connection pool, if I don't do anything, the connection should be automatically returned to the pool, right?

On the other hand, if I close it, is there gonna be any adverse effect on the connection pool (ie, after several calls, there won't be any connection left in the pool?)

score 3 · Accepted Answer · edited May 23 '17 at 12:01

3

The answer is yes, and check Closing JDBC Connections in Pool and JDBC Connection Pooling Best Practices for more information.

edited May 23 '17 at 12:01

Community

1
1

answered Apr 19 '11 at 18:41

Bastardo

4,144
9
41
60

score 1 · Answer 2 · answered Apr 19 '11 at 18:37

1

Yes, you should be closing the connection, if only for quick recovery by the pool.

This article http://www.javaranch.com/journal/200601/JDBCConnectionPooling.html advises placement of a .close() call in a finally block.

answered Apr 19 '11 at 18:37

David Hill

4,102
2
23
19

Do you need to close the connection you get from jdbc connection pool?

2 Answers2

Related