Fix (APAR): PK28415 Status: Fix Release: 5.1.1.10 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK28415 Byte size of APAR: 19205 Date: 2006-08-18 Abstract: Problem in completing the UserWorkArea when an exception is thrown from an included JSP. Description/symptom of problem: PK28415 resolves the following problem: ERROR DESCRIPTION: Workarea service depends on WebAppInitializationCollaborator and WebAppInvocationCollaborator for synchronizing the Workarea state. Unfortunatley WebContainer is not invoking postInvoke(..) method for a jsp if it encounters runtime exceptions. This is causing workarea Service not to synchronize the data correctly and causing a problem. LOCAL FIX: N/A. PROBLEM SUMMARY USERS AFFECTED: Websphere Application Server version 5.1 users who use the interface UserWorkArea. PROBLEM DESCRIPTION: Problem in completing the UserWorkArea when an exception is thrown from an included JSP. RECOMMENDATION: None A com.ibm.websphere.workarea.NotOriginator exception is thrown when trying to complete a UserWorkArea which is started from the same servlet and exceptions are thrown from the included JSP pages before completing. The preinvokes were called on the WebAppInvocationCollaborators before including a JSP page but when exceptions are thrown from the included page then the corresponding postinvokes were not called. PROBLEM CONCLUSION: Changes has been made such that postInvokes on WebAppInvocationCollaborators are called regardless of whether an exception is thrown or not. The code changes for the APAR has been targetted for WAS 5.1.1.13. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release: 5.1 ___ ___ Application Server (Express or BASE) ___ ___ ___ Network Deployment (ND) ___ WebSphere Business Integration Server Foundation (WBISF) Install Fix to: __ 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 PKxxxxx.jar file directly to the maintenance directory 2) Shutdown WebSphere 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 (PKxxxxx.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 WebSphere 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 WebSphere 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 (PKxxxxx.jar). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: