|
Problem |
Very slow or under-powered systems can perform poorly and
produce a variety of error messages. The most common symptoms are very
slow starts and intermittent failures. Modifying selected parameters for
the WebSphere® Application Server V4.0 administrative server and
Application Server processes can overcome some of these limitations and
improve performance. |
|
Solution |
The symptoms of a slow system include:
- Failure of the administrative server to start or a very
slow start. In some cases, CORBA errors are recorded in the
nanny.trace file.
- Failure of the Application Server to start or a possible
timeout in cases where the administrative server process does start.
Administrative server changes:
You can increase the transaction timeout value for the administrative
server to help long operations complete. Add the following two properties
to the admin.config file:
- Change the Transaction Timeout value
from 10 minutes (600 seconds) to 20 minutes (1200 seconds).
- Change the Transaction Inactivity Timeout value
from 1 minute (60000 milliseconds) to 2 minutes (120000 milliseconds)
Default values (The following lines might not be in the admin.config
file.):
com.ibm.ejs.sm.adminServer.tranTimeout=600
com.ibm.ejs.sm.adminServer.tranInactivityTimeout=60000 |
Recommended change (Add the following lines if they are not in the file.):
|
com.ibm.ejs.sm.adminServer.tranTimeout=1200
com.ibm.ejs.sm.adminServer.tranInactivityTimeout=120000 |
Application Server changes:
When you can open the administrative console to connect to a running
administrative server process, you can increase these settings so that the
Application Server can start successfully on a slower system.
Increase the Ping Initial Timeout value on the Advanced tab of the
Application Server to 600 seconds.
Note: After all of the processes start correctly, further
performance improvements are possible.
Customer Example:
One customer was able to change the startup time from 17 minutes to 4
minutes by implementing these configuration changes.
Investigate the other Ping Timeout values referenced in the following
WebSphere Application Server Information Center sections:
|
|
|
|
|
|
|