APAR status |
Closed as program error.
| Error description
Customer has configured WAS to dynacache servlets. The cache
is supposed to find servlets based on the URI specified. JSPs
and servlets specified by the URI are not being found in the
cache but are being re-run to get the results to be sent back to
the browser. Customer ran the snoop servlet a 2nd time and
noticed that the servlet was run again rather than just using t
the cached results.
.
Keywords: WebSphere WAS 3.5.5 dynacache dynamic cache Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Servers users of *
* dynamic caching on 3.5.5 *
****************************************************************
* PROBLEM DESCRIPTION: Servlets not being cached after *
* configuring cache policy. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A URI within a war was specified for a cache policy, but that
servlet was not cached. Problem conclusion
Modified the logic in WebAppServletManager.java to properly
construct a url from the servlet configuration information. Temporary fixComments
APAR information | APAR number | PQ58738 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-03-05 | Closed date | 2002-04-09 | Last modified date | 2002-04-09 |
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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|