Use this page to set advanced properties for your data source. These properties activate and configure services that the application server applies to data sources to customize how connections are used within the application server. These properties do not affect how connections are used by the database.
Specifies the number of statements that can be cached per connection. WebSphere Application Server caches a statement after the user closes it.
In test applications, tuning the statement cache improved throughput by 10-20%. However, because of potential resource limitations, this might not always be possible.
Data type | Integer |
Default | Depends on the database. Most are 10. Informix versions 7.3, 9.2, 9.3, and 9.4, without the respective latest fixes, must be 0. A default of 0 means there is no cache statement. |
If checked, the following warning message is entered in the WebSphere Application Server system out log if multiple threads attempt to concurrently use the same connection handle. You can use this property to debug connection problems if you think the problems might be caused by multiple threads trying to use the same connection handle. Having multiple threads concurrently using the same connection handle is a programming model violation.
J2CA0167W: An attempt to concurrently use the same connection handle by multiple threads has been detected. The connection handle is: {0}.
If checked, there cannot be an exact match on connections retrieved out of the WebSphere Application Server connection pool (that is, connection pool search criteria do not include user name and password). Instead, the reauthentication of connection is done in the doConnectionSetupPerTransaction() of the DataStoreHelper class. Note that WebSphere Application Server runtime does NOT provide connection reauthentication implementation. Therefore, when this box is checked you MUST extend the DataStoreHelper class to provide implementation of the doConnectionSetupPerTransaction() method where the reauthentication takes place. Failure to do that results in wrong connections being handed out to users. For more information, refer to the API documentation for com.ibm.websphere.rsadapter.DataStoreHelper#doConnectionSetupPerTransaction(...).
Connection reauthentication can help improve performance by reducing the overhead of opening and closing connections, particularly for applications that always request connections with different user names and passwords.
If checked, the application server allows JMS to get optimized connections from this data source. This property prevents JDBC applications from sharing connections with CMP applications.
Specifies whether the container tracks cached handles, which are connection handles that an application component holds active across transaction and method boundaries. You can use this property to debug connection problems, but tracking handles can cause large performance overhead during run time.
Specifies whether the container issues an entry to the activity log when an application obtains a connection without a transaction context. These are exceptions to the J2EE programming model connection requirements.
Specifies whether the connection manager tests the validity of pooled connections before returning them to applications. If you select this option, you can specify how often, in seconds, the connection manager retries the connection if the initial attempt fails.
If you select the Pretest existing pooled connections option, you can use the Retry interval field to specify the frequency, in seconds, that the connection manager retries the existing pooled connection, if the initial attempt fails.
Data type | Integer |
Specifies whether the connection manager tests the validity of the initial connection to a database. If you select this option, you can specify the number of times that the connection manager retries the connection and the amount of time the connection manager waits between retries.
If you select the Pretest new connections option, you can use the Number of retries field to specify the number of times to retry the initial connection, if the first attempt fails.
Data type | Integer |
If you select the Pretest new connections option, you can use the Retry interval field to specify the frequency, in seconds, that the connection manager retries the initial connection to a database, if the first attempt fails.
Data type | Integer |
Specifies the SQL statement that the application server sends to the database to test an existing pooled connection or a new connection to a database. Because the pretest operation is designed to test only that a connection makes a round trip to and from the database server, use a simple, low-impact query. A good choice for a PreTest SQL string is a generic query that has minimal potential impact on performance of the application server.
Data type | String |