This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
"meg850", The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at http://www.javaranch.com/name.jsp. We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please edit your profile and select a new name which meets the requirements. Thanks. Dave
Connection pooling is usually done to improve application performance and decrease the load on the database. DriverManager is only responsible for creating new connection to the database. As you probably know, creating a connection and logging in to the database is relatively time-consuming. Therefore, connection pool is often used. A connection pool is like a facade to the DriverManager. Application can use the Connection Pool to ask for a connection to database. Connection Pool caches the connections to the database. This means that once an application ends using a database connection (e.g. at the end of transaction), Connection Pool does not release it, but reuses it when the application asks for the connection again. Anyway, you can find much information on this topic for example here. [ September 09, 2002: Message edited by: Tanel Alumae ]