Configuring BIRT JDBC connection pooling

Caches concurrent connections, so the Factory can reuse them. The default is 10. Increase the pool size to establish more connections. To disable the connection pool, set BIRT JDBC Connection Pool Size to 0. The larger the pool size, the better performance in a highly concurrent system and the greater the memory consumption.

Specifies the time-out interval for cached connections. The default is 3600 seconds. Increasing the available connections increases performance, but also increases memory consumption.

Controls the frequency of BIRT connection validation. Connection validation prevents a query from attempting to use a broken connection. The default value of -1 disables connection validation.

The interval is expressed in seconds. If the value is positive, iHub first determines whether the last validation occurred in the specified interval. If not, iHub performs validation by calling java.sql.Connection.isValid( ). All DataDirect JDBC drivers support java.sql.Connection.isValid( ). Because some JDBC drivers do not support java.sql.Connection.isValid( ), the administrator must stop and start the cluster after rebooting the metadata database to refresh the JDBC connection pool even if the interval has not changed.

1 Stop the BIRT iHub cluster. For information on stopping the cluster, see "Taking the cluster offline," in Chapter 3, "Configuring BIRT iHub to use an alternative database on a Windows platform," or Chapter 4, "Configuring BIRT iHub to use an alternative database on a Linux platform," in the BIRT iHub System Administration Guide.

2 Navigate to the shared configuration directory. For example, if the system administrator created a folder for the shared configuration directory named config_cluster, then in a default BIRT iHub installation on Windows, where BIRT iHub was installed as an individual module, the path to the shared configuration directory is:

3 As a best practice, create a backup copy of acserverconfig.xml. Then, open acserverconfig.xml using a text editor.

4 Find a <Template> element in which you want to configure BIRT JDBC connection pooling. Within that <Template> element, find the <ViewingService> subelement. The following example shows the <ViewingService> subelement of the small <Template> element in the acserverconfig.xml file that installs with BIRT iHub:

<ViewingService

ViewingWeight="100"

FileCacheTimeout="86400"

...

PersistentArchiveFileCacheTimeout="7200"

BIRTReportDesignCacheTotalNumberOfEntries="50"/>

5 Add the BIRT JDBC connection pooling properties as <ViewingService> attributes to the list of <ViewingService> attributes. Use the following guidelines to set values for these properties:

Accept the default value, 10 connections. Alternatively, decrease or increase the pool size by typing a number not less than 0 or greater than 65535.

Accept the default value, 3600 seconds. Alternatively, increase or decrease the time‑out period by typing a different number.

Accept the default value, -1, to leave connection validation disabled. Alternatively, enable connection validation by specifying a period of time in seconds.

The following example shows these properties defined with their default values:

<ViewingService

ViewingWeight="100"

FileCacheTimeout="86400"

...

PersistentArchiveFileCacheTimeout="7200"

BIRTReportDesignCacheTotalNumberOfEntries="50"

BIRTJDBCConnectionPoolSize="10"

BIRTJDBCConnectionPoolTimeout="3600"

BIRTConnectionValidationInterval="-1"/>

6 Perform steps 4 and 5 for each template in which you want to specify BIRT JDBC connection pooling properties. Save and exit the file.

7 Start the BIRT iHub cluster. For information on performing this task, see "How to start the cluster," in Chapter 3, “Configuring BIRT iHub to use an alternative database on a Windows platform," or Chapter 4, "Configuring BIRT iHub to use an alternative database on a Linux platform," in the BIRT iHub System Administration Guide.