Should I close a connection when using DataBase Pool?

Thread view:

JTL.zheng - 08 Nov 2007 14:09 GMT

database pool means that the conncetion can be used by other user.
so when I finish the job, should I call
conn.close();
after it as the old way?

Reply to this Message

Sebastian Millies - 08 Nov 2007 14:55 GMT

Am Thu, 08 Nov 2007 06:09:06 -0800 schrieb JTL.zheng:

> database pool means that the conncetion can be used by other user.
> so when I finish the job, should I call
> conn.close();
> after it as the old way?

Yes. However, you should refer to the documentation of
your pool library to be sure. E. g. it could be like this:
PooledConnection conn = Pool.getConnection();
...
conn.close()
where the implementation of PooledConnection#close()
may choose to return the connection to the pool.

-- Sebastian

Reply to this Message

Wojtek - 08 Nov 2007 15:58 GMT

Sebastian Millies wrote :

> Am Thu, 08 Nov 2007 06:09:06 -0800 schrieb JTL.zheng:
>
[quoted text clipped - 10 lines]
> where the implementation of PooledConnection#close()
> may choose to return the connection to the pool.

As noted above, you should alwasy explicitly close connections (and
result sets, and cursors, and statements, and ...).

Some pool managers (proxool for example) will automatically clean up
connection resources such as statements and result sets.

And proxool will also close connections after a certain number of
seconds.