PQ60896: WAS355 - HIGH CPU SPIKES FOR ADMIN SERVER PROCESS

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
Customer running WAS 355 and servlet redirector. His
configuration consists of a WAS machine and a webserver machine
running servlet redirector. The problem he is seeing is that his
admin server cpu spikes very often. The customer does not have
any ejbs. He has 300 uris. After several tests it was confirmed
that the cpu was spiking first time the uri was retrieved from
repository and cached in to memory. However, it was very unusual
that this had to be done for each user. The customer is using
url rewriting.
This apar belongs to engine component.
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of 3.5    *
*                 with ServletRedirector and URL Rewriting     *
*                 turned on and having many URI's defined      *
*                 for the AppServer                            *
****************************************************************
* PROBLEM DESCRIPTION: Enabing Servlet Redirector causes       *
*                      high CPU utilization in the             *
*                      AdminServer, making the application     *
*                      unusable                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The IIOPRedirector (ServletRedirector) is not stripping off the
jsessionid when URL rewriting is turned on.  This causes the URI
to be unique whenever the session id changes forcing the
servletRedirector to query the database instead of getting the
URI from the cache.  This causes high CPU utilization and slow
response times.
Problem conclusion
InvocationCache was caching the uri with the jsessionid
appended, stripping off the jseesionid before the uri cached
solves the problem for subsequent requests.
Temporary fix
Comments
APAR information
APAR numberPQ60896
Reported component nameWAS STANDARD AI
Reported component ID5648C8300
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-05-07
Closed date2002-06-05
Last modified date2002-06-05

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

Fix information
Fixed component nameWAS STANDARD AI
Fixed component ID5648C8300
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ60896
IBM Group: Software Group
Modified date: 2002-06-05