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 fixProblem 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 fixComments
APAR information | APAR number | PQ51120 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-08-01 | Closed date | 2001-08-08 | Last modified date | 2001-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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R300 PSY | UP | R350 PSY | UP |
|