Copyright © 2001-2017 Giles Winstanley Updated: 15 October 2017Version: 7.0.2 A Java-based database connection pooling utility, supporting time-based idle timeout, statement caching, connection validation, and easy configuration using a pool manager.
Applications using databases often need to obtain connections to the database frequently.
Various factors may affect your decisions, such as licence restrictions, system resources, etc.
Many databases will close any unused connections once a certain time has elapsed (e.g. It makes no sense to set to longer than this, so an obvious choice would be a non-zero smaller time period.
You should also check pooling performance under both low and high load scenarios.
Another quick way is to download this JAR file and launch it at the command-line by typing: after navigating to the download directory (it contains a single Java class just to show a little additional useful information).For other scenarios, the DBPool JAR file must be in a location where it's accessible by the host application.For standalone applications this usually means in the CLASSPATH, and for web containers there is usually a specific directory recommended for JAR libraries (for example, when used with Apache Tomcat it can be placed in the Each connection within a pool connects to the same database source using the same authentication.If you need to ask for help or raise an issue, please use the project issue tracker, and include as much information as possible to help diagnose the problem, including the version of DBPool in use, relevant stacktraces, log files (with debug option enabled), source code, and properties file where appropriate. If using DBPool via a dependency management system (e.g.Apache Maven, Ivy) then simply add it as a dependency in your configuration as usual.