PQ51120: WEBBAPP NOT ALIVE


APAR status
Closed as program error.

Error description
There is a problem with the webapp id not being cleared from the
cache after it has been restared causing WAS to point to the
cached copy. Sinvce this ID is no longer valid, it results in
a WEBAPP not Alvie error.
 There is all ready a defect open, 109276
Local fix
Problem summary
WebApp is not alive was resolved along with an invocation cache
problem via this defect.
Problem conclusion
CachedObjectSupport.invalidateCachedObjects().  It was getting
an enumeration but then deleting elements from the enumeration
while still holding the enumeration (co.invliadate() eventually
calls back to cachedobjectsupport.removeCachedObject). In
correcting this problem, the long standing WebApp is not alive
has also been resolved.
Temporary fix
Comments
APAR information
APAR numberPQ51120
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-08-01
Closed date2001-08-08
Last modified date2001-08-08

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
ENGINE
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R300 PSYUP
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ51120
IBM Group: Software Group
Modified date: 2001-08-08