JDBC connection pooling : Java Glossary

Tips

• 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 Oracle TopLink.
• 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 JDBC datasource documentation.
• 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 SQL commands.
• 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.

Learning More