JDBC connection pooling : Java Glossary
- JDBC connection pooling
There is quite an overhead to setting up a connection to an
SQL (Standard Query Language) database via JDBC (Java Data Base Connectivity).
You want to avoid doing it if possible for every transaction. On the other hand,
there is a fair overhead for each connection and sometimes a fairly small limit on
the simultaneous number of connections enforced by licencing. So you can’t very
well leave a connection open per session. JDBC
connections are single thread, so you cannot easily use a single connection for
mulitiple purposes. The solution is to use a pool of connections, which works much
like a pool of corporate vehicles. The pool of connections stay open, with a
connection assigned to only a single given purpose at a time. Happily, it is unlikely
you will need to write your own code to manage the pool of connnections.
- A web application has to explictly close ResultSets,
Statements and Connections.
Failure to close these resources results in them never being available again for
reuse — a db connection pool leak. You will
eventually run out of connections.
- Try to stay away from third party jars. If JDBC
is enough, build on Tomcat.
- If you need JPA or EJB3, go with JBoss
or GlassFish. JBoss has Hibernate
with it, while GlassFish has
- If you go with Hibernate, try to
stick with JPA, do not use any Hibernate specific features.
- If you take MVC design, you need third
party jars for the implementation if you go with Tomcat. It does not have even the standard JSF in it. Tomcat
would need maybe Apache MyFaces, while
JBoss or GlassFish come with some implementation already there.
- In Tomcat, read up on how configure a DataSource to a connection pool in the
JNDI (Java Naming and Directory Interface) and
- Even though it looks as though you are using a PreparedStatement only once, behind-the-scenes code miraculously
manages to recycle them. PreparedStatement also protects
you from stray characters in your data from being interpreted as
- In addition to putting JNDI
code in your Servlet, you must configure the servlet womb. That will likely include
making a special jar available to the Servlet womb.