Setting up connection pools
Opening and closing database connections is a relatively slow operation. For performance reasons, GlassFish and other Java EE application servers keep a pool of open database connections. When a deployed application requires a database connection, one is provided from the pool, when the application no longer needs the database connection, said connection is returned to the pool.
The first step to follow when setting up a connection pool is to copy the JAR file containing the JDBC driver for our RDBMS in the lib directory of the domain (consult your RDBMS documentation for information on where to obtain this JAR file). If the GlassFish domain where we want to add the connection pool is running when copying the JDBC ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access