Fix (APAR): PK15540 Status: Fix Release: 5.1.1.6,5.1.1.5,5.1.1.4,5.1.1.3,5.1.1.2,5.1.1.1,5.1.1,5.1.0.6,5.1.0.5,5.1.0.4,5.1.0.3,5.1.0.2,5.1.0.1,5.1 Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK15550 Byte size of APAR: 5616085 Date: 2005-12-12 Abstract: The Edge Side Include (ESI) statistics were not returned to the user with correct values. All the values were reported as 0 even though the plug-in has cached the response. Description/symptom of problem: PK15540 resolves the following problem: ERROR DESCRIPTION: Prob Desc: The request sent by the ESI processor of the WAS side to collect statistics is not read by the plug-in. It is sitting in the read queue of the TCP stack After further testing, the connection initiated by plug-in is readable/writable for only around 30 sec. Then, plug-in doesn't get access to the socket data. The data is pending in the receive queue of the TCP stack. The scenario happened since the signal SIGALRM sent by the IHS parent pr ocess was received by the ESI monitor thread instead of the original plug-in thread started by the IHS process. The reported scenario is resolved when the ESI monitor thread started by the plug-in blocks all the OS signals. LOCAL FIX: No work around available PROBLEM SUMMARY USERS AFFECTED: All users of web server plug-in for WebSphere Application Server when ESI invalidation Emonitor is enabled. PROBLEM DESCRIPTION: The Edge Side Include (ESI) statistics were not returned to the user with correct values. All the values were reported as 0 even though the plug-in has cached the response. RECOMMENDATION: None The request to collect statistics was not received by the plug-in thread. This happened since the parent web server process had issued a SIG_ALRM signal and it was received by the ESI (Edge Side Include) monitor thread instead of the plug-in thread which is handling the request. The ESI monitor thread should block all the synchronization signals sent by the parent web server process. PROBLEM CONCLUSION: The web server plug-in is enhanced to block all the synchronization signals sent by the parent web server process. This allows the plug-in to receive the Edge Side Include (ESI) statistics gather request from the application server. The fix for this APAR is currently targeted for inclusion in fixpack 5.0.2.15, and 5.1.1.9. Please refer to the Recommended Updates page for delivery information: http://www-1.ibm.com/support/docview.wss? rs=180&context=SSEQTP&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release: 5.0 5.1 ___ ___ Application Server (Express or BASE) ___ Enterprise Edition (DD) ___ ___ Network Deployment (ND) ___ ___ Edge Components ___ ___ Developers Edition ___ ___ Tools ___ WebSphere Business Integration Server Foundation (WBISF) Y Web server plug-in Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files. 1) Copy PK15540*.jar file directly to the maintenance directory 2) Shutdown Web server Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PK15540*.jar file which was copied in the maintenance directory). The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory. 7) Install the maintenance package. 8) Restart Web server Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown Web server Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PK15540*.jar). 6) UnInstall maintenance package. 7) Restart Web server Directions to re-apply fix: 1) Shutdown web server. 2) Follow the Fix instructions to apply the fix. 3) Restart web server. Additional Information: