PQ66154: ORPHAN/IDLE TIMEOUT FOR ADMINSERVER IN WAS 3.5 DON'T WORK

Fixes are available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)
3.5.4-3.5.7, 4.0.2-4.0.7: Component cumulative Connection Manager fix

APAR

APAR status
Closed as program error.

Error description
rphan and idle timeout values can be set in admin.config in WAS
4.0 as follows:
.
com.ibm.ejs.sm.adminServer.dbidleTimeout=150
com.ibm.ejs.sm.adminServer.dborphanTimeout=150
.
This does not work on my WAS 354 system. There's no error
indicating these values are incorrect.
.
'cm' and 'sm' teams need to work together to make this work in
WAS 3.5.
4.0 as follows:.com.ibm.ejs.sm.adminServer.dbidleTimeout=150com.ibm.ejs.sm.adminServer.dborphanTimeout=150.This does not work on my WAS 354 system. There's no errorindicating these values are incorrect..'cm' and 'sm' teams need to work together to make this work inWAS 3.5.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: All users running WebSphere Application      *
*                 Server 3.5.4 or later needing to modify      *
*                 AdminServer DataSource properties            *
****************************************************************
* PROBLEM DESCRIPTION: Admin Repository DataSource settings    *
*                      not available on WAS3.5                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Orphan and idle timeout values for AdminServer can be set in
admin.config in WAS 4.0 as follows:
 .
 com.ibm.ejs.sm.adminServer.dbidleTimeout=150
 com.ibm.ejs.sm.adminServer.dborphanTimeout=150
 .
These and other AdminServer DataSource properties are not
available on a WAS354 system.
admin.config in WAS 4.0 as follows:.com.ibm.ejs.sm.adminServer.dbidleTimeout=150com.ibm.ejs.sm.adminServer.dborphanTimeout=150.These and other AdminServer DataSource properties are notavailable on a WAS354 system.
Problem conclusion
This fix allows a user to specify datasource properties such
as idle timeout and orphan timeout for the datasource used by
the WebSphere Administrative Server.  These properties are set
by adding entries to the admin.config file.  The possible
datasource properties are:

com.ibm.ejs.sm.adminServer.connectionPoolSize
 - The maximum number of connections in the Administrative
   Server connection pool. The default value is 15.
com.ibm.ejs.sm.adminServer.connectionPoolSizeMin
 - The minumum number of connections in the Administrative
   Server connection pool.  The default value is 1.
com.ibm.ejs.sm.adminServer.dbconnTimeout
 - Amount of time in milliseconds to wait for a connection
   from the connection pool before issuing a
   ConnectionWaitTimeoutException.  The default value is
   180000, or 3 minutes.
com.ibm.ejs.sm.adminServer.dbidleTimeout
 - Amount of time in milliseconds a connection will remain
   idle in the pool before being closed.  The default value
   is 1800000, or 30 minutes.  If the pool is already at the
   connectionPoolSizeMin value, connections will not be idled.
com.ibm.ejs.sm.adminServer.dborphanTimeout
 - Amount of time in milliseconds before a connection which
   has not been properly closed will be returned to the
   connection pool.  The default value is 1800000, or 30
   minutes.
com.ibm.ejs.sm.adminServer.dbstatementCacheSize
 - The maximum number of prepared statement to be cached for
   the datasource.  This value will be divided by the
   connectionPoolSize value, and that number of prepared
   statements will be cached per database connection in the
   pool.  The default value is 20 prepared statements per
   connection.

For more details on the meanings of the above values, or for
more details on how connection pooling works, see
http://www-3.ibm.com/software/webservers/appserv/
whitepapers/connection_pool.pdf.  While this comprehensive
connection pooling whitepaper was written for WebSphere 4.0,
most of the concepts apply to WebSphere 3.5 as well, and
features only available in WebSphere 4.0 are flagged as such.
datasource properties are:com.ibm.ejs.sm.adminServer.connectionPoolSize- The maximum number of connections in the AdministrativeServer connection pool. The default value is 15.com.ibm.ejs.sm.adminServer.connectionPoolSizeMin- The minumum number of connections in the AdministrativeServer connection pool. The default value is 1.com.ibm.ejs.sm.adminServer.dbconnTimeout- Amount of time in milliseconds to wait for a connectionfrom the connection pool before issuing aConnectionWaitTimeoutException. The default value is180000, or 3 minutes.com.ibm.ejs.sm.adminServer.dbidleTimeout- Amount of time in milliseconds a connection will remainidle in the pool before being closed. The default valueis 1800000, or 30 minutes. If the pool is already at theconnectionPoolSizeMin value, connections will not be idled.com.ibm.ejs.sm.adminServer.dborphanTimeout- Amount of time in milliseconds before a connection whichhas not been properly closed will be returned to theconnection pool. The default value is 1800000, or 30minutes.com.ibm.ejs.sm.adminServer.dbstatementCacheSize- The maximum number of prepared statement to be cached forthe datasource. This value will be divided by theconnectionPoolSize value, and that number of preparedstatements will be cached per database connection in thepool. The default value is 20 prepared statements perconnection.For more details on the meanings of the above values, or formore details on how connection pooling works, seehttp://www-3.ibm.com/software/webservers/appserv/whitepapers/connection_pool.pdf. While this comprehensiveconnection pooling whitepaper was written for WebSphere 4.0,most of the concepts apply to WebSphere 3.5 as well, andfeatures only available in WebSphere 4.0 are flagged as such.
Temporary fix
posted test fix jar file on wasdoc0, wait for customer update
Comments
APAR information
APAR numberPQ66154
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-09-12
Closed date2002-09-26
Last modified date2002-09-26

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
ADMINSVR
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ66154
IBM Group: Software Group
Modified date: 2002-09-26