Use the following settings to increase performance for
WebSphere Application Server V3.5 and V4.0 releases.
- Set the adminserver transaction and inactivity timeout
properties in the admin.config file to a value that allows a long clone
operation to complete. To increase the default transaction timeout for the
admin server, add the following two properties to the admin.config file :
- com.ibm.ejs.sm.adminServer.tranTimeout=<time in seconds,
default 600>
- com.ibm.ejs.sm.adminServer.tranInactivityTimeout=<time in
milliseconds, default 60000>
- Setting noLocalCopies=true (This is set by default in V4.0
releases; it must be manually set for V3.5 releases).
Setting the no local copies option on
the adminserver causes the adminserver to pass parameters by reference,
rather than by value. To set this parameter, edit the admin.config file
for each of your adminservers and add the following two properties
(separated by a space) to the
com.ibm.ejs.sm.util.process.Nanny.adminServerJvmArgs parameter:
- -Djavax.rmi.CORBA.UtilClass=com.ibm.CORBA.iiop.Util
- -Dcom.ibm.CORBA.iiop.noLocalCopies=true
- Change the adminserver JVM™ heap settings from -ms128m
-mx256m to -ms48m -mx256m. To change this setting in the
admin.config file for each of your adminserver, edit the following line:
com.ibm.ejs.sm.util.process.Nanny.adminServerJvmArgs=-Djavax.rmi.CORBA.UtilClass\=com.ibm.CORBA.iiop.Util\
-Dcom.ibm.CORBA.iiop.noLocalCopies\=true\ -Xms48m -Xmx256m\ -Xminf0.15\
-Xmaxf0.25
- Disable automatic plug-in config generation:
Workaround to stop the PlugIn Regen:
- Create a new properties file called global.properties in the
properties directory (WebSphere/AppServer/properties).
- Enter the following line in the global.properties file:
com.ibm.servlet.engine.disableAutoPluginCfg=true
- Stop and restart the adminserver. Check the time stamp in the temp
directory to confirm.
- Set the parameter for disabling URI checking for each
adminserver node (PQ51576 is required prior to PTF5 of WebSphere
Application Server 3.5). Add the following line to the admin.config file:
com.ibm.ejs.sm.adminServer.uriCheck=false
- Increase the adminserver container cache size on each
adminserver node. WebSphere Application Server has a
hard-coded limit on the cache used by the EJB™container operating inside of the
adminserver. When a large number of resources
are configured in WebSphere Application Server, the following
parameters need to be added to tune the cache (PQ45602 is needed prior to
PTF4 of WebSphere Application Server 3.5).
com.ibm.ejs.sm.adminServer.containerCacheSize= (default value
2047)
com.ibm.ejs.sm.adminServer.containerCacheSoftLimit= (default value
2000)
com.ibm.ejs.sm.adminServer.containerCacheHardLimit= (default value
2047)
com.ibm.ejs.sm.adminServer.containerCacheSweepInterval= (default
value 1000)
The CacheSweepInterval is the time in milliseconds between sweeps.
The default is 1000 msec, and there is no obvious reason to change it. All
the other values are numbers of objects. Roughly, the number of objects in
the cache corresponds to the total number of objects in the WebSphere
repository (for example, number of nodes + number of servlets + number of
EJBs + number of URI entries + .... ). It is suggested
to start with 8191/8000/8191/1000 respectively
and increase as needed. The CacheSoftLimit should be slightly less than
the CacheHardLimit.
- If you use DB2® for the repository, set the
applheapsz and the app_ctl_heap_sz settings to 512 (recommended) or
higher, depending on the number of objects in the repository. To check or
set these parameters, use the following commands:
To find the current size of
applheapsz/app_ctl_heap_sz, run
db2 get db cfg for database name
To increase the size of applheapsz/app_ctl_heap_sz,
run:
db2 update db cfg for database name
using applheapsz/app_ctl_heap_sz new heap size in 4 KB
blocks
|