PQ74418: cachemonitor:For some reason, the first ESI Processor does not get removed from the list of processors,hanging the application | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description cachemonitor: invoke a few esi cached pages. Call the cachemonitor and view the cache. You will see 1 ESI Processor. stop, then start the HTTP server. Call the cachemonitor and view the cache (May need to hit the refresh cache button). You will see 2 ESI Processors and some uninitialized data (-1s). Press refresh again, and the application hangs. Problem is caused by the cachemonitor iterating through the ESI Processors to tally up the data. For some reason, the first ESILocal fix Processor oes not get removed from the list of processors, so when the cachemonitor asks for data to be read in via ESI Processor 1 from its connection with the plugin, I *think* it ends up sitting on the socket read, thus hanging the application. I say *think* because I would expect the socket read to just fail rather than block, so perhaps it is stuck somewhere else. LOCAL FIX:ン Dynacache defect 161746 addresses the reported scenarioProblem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users of * * DynaCache and the CacheMonitor application. * **************************************************************** * PROBLEM DESCRIPTION: If a user restarts the Web server while * * viewing Edge statistics hangs the * * CacheMonitor application. * **************************************************************** * RECOMMENDATION: * **************************************************************** If the Web server is restarted while viewing the Edge cache statistics in the CacheMonitor, the first Edge Side Include ( ESI ) Processor is not removed from the list of processors. This will cause the CacheMonitor application to hang.Problem conclusion The ESIProcessor.java file was modified so it will not wait for a response from a Web server process that is no longer alive.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ74418
IBM Group: Software Group
Modified date: Aug 7, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.