Fix (APAR): PK21264 Status: Fix Release: 5.0.2.9,5.0.2.8,5.0.2.7,5.0.2.6,5.0.2.5,5.0.2.4,5.0.2.3,5.0.2.2,5.0.2.15,5.0.2.14,5.0.2.13,5.0.2.12,5.0.2.11,5.0.2.10,5.0.2.1,5.0.2 Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: PK21264 Byte size of APAR: 16033 Date: 2006-04-10 Abstract: TPV Log playback hangs Description/symptom of problem: PK21264 resolves the following problem: ERROR DESCRIPTION: WAS5.0.2.6 ND WP5.0.2.2 Customer wants to monitor WebSphere Portal(WP) with TPV If using TPV on client machine where WP is not installed, TPV client almost works with no problem. However, if trying to view the binary log of TPV collected from WP, TPV hangs Extracted from tperfviewer_debug.log: [RAUtils] getProcessType(): Detected on 9.189.57.68:8880:SOAP com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: Failed to make the SOAP RPC call: invoke at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT emplate(SOAPConnectorClient.java:594) ---- Begin backtrace for nested exception [SOAPException: faultCode=SOAP-ENV:Client; msg=com.ibm.ws.pmi.server.PerfLevelDescriptor; Local class not compatible: stream classdesc serialVersionUID=2807497595173060747 local class serialVersionUID=-5934872678821227124; targetException=java.lang.IllegalArgumentException: com.ibm.ws.pmi.server.PerfLevelDescriptor; Local class not compatible: stream classdesc serialVersionUID=2807497595173060747 local class serialVersionUID=-5934872678821227124] LOCAL FIX: n/a PROBLEM SUMMARY USERS AFFECTED: All users using Tivoli Performance Viewer (TPV) log playback PROBLEM DESCRIPTION: TPV Log playback hangs RECOMMENDATION: apply this fix TPV log playback hangs due to an inconsistency in accessing the mbean when WebSphere Portal Server is installed. PROBLEM CONCLUSION: This APAR fixes the problem by ensuring a consistent mbean invovation for different components. The fix for this APAR is currently targeted for inclusion in cumulative fix 5.02.17. 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: 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) 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 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: