Resin provides a robust and tested connection pool that is used to obtain connections to databases.
A basic <database> configuration specifies the following:
This <database> will configure a javax.sql.DataSource and store it in JNDI at java:comp/env/jdbc/test_mysql. To use the data source, follow the database use pattern in the DataSource tutorial.
Sample <database> configurations are available in the thirdparty driver page.
Although some deployments will specify driver and connection pool parameters, the default values will be fine for most applications.
A database connection is used to allow the Java program, running in a JVM, to communicate with a database server.
Connection pools are used to reduce the overhead of using a database. Establishing a connection to the database is a costly operation. A connection pool keeps a pool of open connections, each connection can be used for a time as needed, and then released back to the pool. A connection that has been released back to the pool can then be reused.
Connection pooling is especially important in server applications. The overhead of opening a new connection for each new client request is too costly. Instead, the database pool allows for a connection to be opened once and then reused for many requests.
Resin provides an implementation of DataSource. Resin's implementation of DataSource is a connection pool.
A Driver provides an interface and is responsible for the communication with the database. Every different database (i.e Oracle, MySQL) has their own means of enabling communication from the client (in this case Resin and you applications) and the database. The Driver provides a common interface that hides the details of that communication.
Transactions are especially important in server applications where many threads of processing may be interacting with the database at the same time.
For a simple example, imagine a set of operations that reads a value, calculates a new value, and then updates the database.
Imagine if one thread is performing this operation, and in the middle of this read/calculate/update, another thread performs an update. The data that the first thread obtained from the read and is using for the calculation and update is no longer valid.
Placing the read/calculate/update operations in a transactions guarantees that only one thread can perform those operations at a time, if a second thread comes along and tries to perform the operation, it will have to wait for the first thread to finish before it can begin.
If the guarantees that transactions apply need to apply to operations that occur on two databases within the same transaction, distributed transactions are needed.
If A and B in the following example are in two different databases, then a distributed transaction is needed:
Distributed transactions are rarely needed, and few databases really support them.
child of: server, host-default, host, web-app-default, web-app
Configure aresource, which is a database pool that manages and provides connections to a database.
All times default to seconds, but can use longer time periods:
The class that corresponds to <database> is class com.caucho.sql.DBPool
child of: database
Configure a database. The driver is a class provided by the database vendor, it is responsible for the communication with the database.
The jar file with the driver in it can be placed in WEB-INF/lib, although it is often best to place your datbase driver's jar file in $RESIN_HOME/lib/local/, which makes the driver available to all of your web applications.
Examples of common driver configurations are in Third-party Database Configuration .
The class that corresponds to <driver> is class com.caucho.sql.DriverConfig
Database vendors usually provide many different classes that are potential candidates for. The JDBC api has developed over time, and is now being replaced by the more general JCA architecture. The driver you choose depends on the options the vendor offers, and whether or not you need distributed transactions.
JCA is replacing JDBC as the API for database drivers. JCA is a much more flexible approach that defines an API that can be used for any kind of connection, not just a connection to a database. If a database vendor provides a JCA interface, it is the best one to use.
A JCA driver implements ManagedConnectionFactory. When you specify such a class for, Resin will notice that it is a JCA driver and take advantage of the added functionality that the JCA interface provides.
The same JCA driver is used for both non-distributed and distributed transactions
JDBC 2.0 defined the interface. A ConnectionPoolDataSource is not a connection pool, but it does provide some extra information that helps Resin to pool the connection more effectively.
A driver that implementsis better than a JDBC 1.0 driver that implements .
JDBC 2.0 defined the interfacefor connections that can participate in . A distributed transaction is needed when transactions involve multiple connections. For example, with two different database backends, if the guarantees that transactions apply need to apply to operations that occur on both databases within the same transaction, distributed transactions are needed.
Distributed transactions are rarely needed, and few databases really support them. Some vendors will provide XADataSource drivers even though the database does not really support distributed transactions. Often, XADataSource drivers are slower than their ConnectionPoolDataSource counterparts.
XADataSource should only be used if distributed transactions are really needed, and can probably be safely ignored for most applications.
is the original JDBC interface, and is the least desirable kind of driver to use. Resin can still pool database connections using these drivers, but it will not be as efficient as the newer drivers.
is used to set properties of the database driver that are specific to the driver and are not generic enough for resin to provide a named configuration tag.
For example, MySQL drivers accept the useUnicode parameter, if true the driver will use Unicode character encodings when handling strings.
Pooling configuration controls the behaviour of Resin's pooling of database connections. For most applications and databases the only needed change is to increase the max-connections value to meet high demand. Other pooling parameters have defaults that are based on our years of experience with many different databases in many different applications. Changes from the defaults should only be done in response to specific problems, and with a good understanding of how pooling works.
Resin's database pool can test if the pooled database connection is still alive by configuring a pooling parameters are changed from their default values.query. This is typically only necessary if the
If the pool is configured with a long max-idle-time the database connection may become stale if the database is restarted, or if the database is configured with a shorter connection timeout value than the configuration of the Resin pool. Normally when a database connection is returned to the pool it will wait there until the next request or the idle-time expires. If the database goes down in the meantime or closes the connection, the connection will become stale. Theconfiguration can test the database connection.
When pinging, Resin's DBPool will test a table specified with theparameter before returning the connection to the application. If the ping fails, the connection is assumed to be no good and a different connection from the pool is returned. For a ping-table of my_table, Resin will use a query like the following:
You can test the database reliability using the following steps:
The DataSource is a factory that is used to obtain a connection. The DataSource is obtained using the <jndi-name> specified when configuring the database resource.
Ideally, the JNDI lookup of DataSource is done only once, the DataSource obtained from the lookup can be stored in a member variable or other appropriate place. The stored DataSource can then be used each time a connection is needed. If it is not stored, there will be an impact on performance from having to do the lookup each time you want to get a connection.
A connection is obtained from the DataSource. The connection is used as needed, and then released with a call to close() so that Resin knows it is available for a subsequent request.
It is very important that the close() is always called, even if there as an exception. Without the close(), Resin's database pool can loose connections. If you fail to close() a connection, Resin does not know that it is available for reuse, and cannot allocate it for another request. Eventually, Resin may run out of connections.
Always put a close() in a finally block, to guarantee that it is called.
The following example shows the use of a finally block that contains the close(). Because the close() is in a finally block, it will happen even if the code using the connection throws an exception.