With most databases, there is a significant performance overhead incurred when opening and closing database connections. For this reason, most modern application servers implement the idea of connection pooling. They maintain a pool of available database connections that are shared among all the incoming web server requests. When the web server receives a new request for a page, the application server uses an existing connection from the pool (if one is available), processes the request, and then returns the connection to the pool. If no connection is available, the requesting thread waits until one becomes available. The zeroCode-generated application includes such a connection-pooling facility, thus enhancing the throughput and reliability of your site .

The database Connection Pool Management is now highly configurable.
It allows you to decide how scalable you want your connection pool to be. You get to decide the following:

• The Pool size - the number of connections you want ·
• The number of times a thread should retry if it fails to get a connection
• The interval between retries
  These parameters are specified in the config file