Fix (APAR): PK68488 Status: Fix Release: 6.1.0.21 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: 532015 Byte size of APAR: 61485 Date: 2008-11-19 Abstract: When Common Event Infrastructure has difficulty loading the class specified by the "customEventSelectorFilterClass" property, all error messages are discarded. This causes users n Description/symptom of problem: PK68488 resolves the following problem: ERROR DESCRIPTION:? When Common Event Infrastructure (CEI) has difficulty loading the class specified by the "customEventSelectorFilterClass" property, all error messages are discarded. Support is unable to determine the source of failure from the logs because the CEI message is printed at a trace level, not a SEVERE level. LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All WebSphere Application Server users that configure Common Event Infrastructure (CEI) to use for events filtering and classifications a custom defined event selector class. PROBLEM DESCRIPTION: When Common Event Infrastructure has difficulty loading the class specified by the "customEventSelectorFilterClass" property, all error messages are discarded. This causes users not to be able to identify correctly the root cause of the problem. Support is unable to determine easy enough the source of failure from the logs because the CEI message is printed at a trace level, not a SEVERE level. RECOMMENDATION: None When the Common Event Infrastructure code does create an instance of the custom event filter class the error handling code subset does not contain an explicit message to be written in the logs indicating the root cause of the problem. The current message "Failure to initialize custom event selector filter " indicates that a problem has been encountered but only at trace level. PROBLEM CONCLUSION:? An explicit error message has been added specifying the success or failure of initializing the custom event selector class. When using a custom event selector class the logs will contain a message like ?Successfully initialized custom event selector filter. Class : ? followed by the class name when successful. Or ?Failure to initialize custom event selector filter. Class ?. In addition the log indicates the potential action to be taken: ?Verify if the class is added at the event group properties. Verify that the correct class name is added at the event group properties. Verify if the class is in the correct classpath.? The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.23. 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: 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 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) 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.1.0.13 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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.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: