APAR status |
Closed with unknown close code.
| Error description
Customer using a CustomRegistry and running a load test with 100
stress clients that do the following:
- authenticate using a Trust Association & the custom registry
- fetch a single JSP page
- pause 10 seconds
- leave the site. NO LOGOUT
- repeat
The clients use userids out of a possible population of about
10,000 userids. Thus, over a reasonable period of time, WAS will
see 10,000 unique userids.
The admin server, over a long period of time, logs out of memory
errors. In this case, it took 4 hours. stress clients that do the following: - authenticate using a Trust Association & the custom registry- fetch a single JSP page- pause 10 seconds- leave the site. NO LOGOUT- repeatThe clients use userids out of a possible population of about10,000 userids. Thus, over a reasonable period of time, WAS willsee 10,000 unique userids.The admin server, over a long period of time, logs out of memoryerrors. In this case, it took 4 hours. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users who *
* have enabled security using LTPA *
* authentication. *
****************************************************************
* PROBLEM DESCRIPTION: Slow performance and high CPU usage *
* during security cache cleaning cycles *
* and possible OutOfMemoryExceptions. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Slow performance and high CPU usage during security cache
cleaning cycles and possible OutOfMemoryExceptions. These
issues are seen on servers with a large number of different
users (12000 on the reported system) accessing the system
within the security cache timeout period. The performance
problem was a result of the cache cleaning algorithm which
evaluated each cache entry as to whether or not it needed to
remain in the cache. The out of memory condition was a
result of the algorithms failure to remove cache entries. Problem conclusion
The cache cleaning algorithm was changed to evaluate all cache
entries inserted into the cache within a similar time period
(one half the security cache timeout) at the same time. The
new algorithm guarantees that the vast majority of entries
will stay in the cache for the minimum of the security cache
time out. There is now the potential for a small number of
cache entries to be flushed from the cache early or for a
cache miss to occur when there should have been a hit. This
is negligible in comparison to the amount of time saved in
cache cleaning, however. Temporary fixComments
APAR information | APAR number | PQ38019 | Reported component name | WEBSPHERE AE SO | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED | PE | NoPE | HIPER | NoHIPER | Submitted date | 2003-03-03 | Closed date | 2003-03-03 | Last modified date | 2003-03-17 |
APAR is sysrouted FROM one or more of the following: PQ62260
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:PQ62260
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WEBSPHERE AE SO | Fixed component ID | 5648C8402 |
Applicable component levels | R400 PSY | UP |
|