Fix (APAR): PK30530 Status: Fix Release: 6.1.0.3,6.1.0.2,6.1.0.1,6.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PK30530 Byte size of APAR: 15842 Date: 2007-03-21 Abstract: If an exception destination for a destination is set to "" (a blank field) using wsadmin, messages will continue to be sent to the system exception destination when they should be Description/symptom of problem: PK30530 resolves the following problem: ERROR DESCRIPTION: When "Exception Destination" is set to "None", the messages are incorrectly moved to System exception destination afterthe no. of retries are exhausted. LOCAL FIX: The problem is due to the test on the exception destination field inmethod isBlockRequired in class ExceptionDestinationHandlerImpl.java checking for null whereas it should check for null or "". PROBLEM SUMMARY USERS AFFECTED: Users of WebSphere Application Server versions 6.0.x and 6.1.x using default messaging. PROBLEM DESCRIPTION: If an exception destination for a destination is set to "" (a blank field) using wsadmin, messages will continue to be sent to the system exception destination when they should be left on the original destination. RECOMMENDATION: None A missing check for an empty field in the exception destination setting for a destination resulted in messages that should have remained on the destination being sent to the system exception destination. PROBLEM CONCLUSION: The fix adds a check for an empty field as well as null on the exception destination setting before sending messages to the system exception destination. Directions to apply fix: Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) 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. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak 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.pak file which was copied in the maintenance 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.pak). 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: