Application servers typically provide administrative tools to maintain idle timeouts for connections in their pool. When the timeout is exceeded, the application server closes the connection and removes it from the pool.
Application servers might support global timeouts in an implementation specific way or might honor the timeout properties specified in a ConnectionPoolDataSource object. The IdmsConnectionPoolDataSource class supports the maxIdleTime and propertyCycle properties as recommended in the JDBC 4.0 specification. The effective idle time for an application server that uses these or equivalent properties could be as large as the sum of the two intervals. The Type 4 JDBC driver uses these properties to adjust the RESOURCE TIMEOUT INTERVAL of the task automatically. You may need to specify the equivalent idle time property in both the application server's ConnectionPoolDataSource implementation and as a custom property for the IdmsConnectionPoolDataSource that it references.
Note: Not all application servers use these properties.
The idle timeout set for a pooled connection should be shorter than the idle timeouts set closer to the CV, possibly by as much as 300 to 600 seconds.
|
Copyright © 2009 CA.
All rights reserved.
|
|