PK21264; 5.0.2.9: Tivoli performance viewer hangs on
client machine
Downloadable files
Abstract
Tivoli@ performance viewer Log playback hangs.
Download Description
PK21264 resolves the following problem:
ERROR DESCRIPTION:
WebSphere@ Application Server V5.0.2.6
WebSphere Portal V5.0.2.2
Customer wants to monitor WebSphere Portal with Tivoli performance viewer.
If using Tivoli performance viewer on client machine where WebSphere
Portal is not installed, Tivoli performance viewer client almost works
with no problem. However, if trying to view the binary log of Tivoli
performance viewer collected from WebSphere Portal, Tivoli performance
viewer hangs
Extracted from tperfviewer_debug.log:
[RAUtils] getProcessType(): Detected <UnManagedProcess> 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.invokeTemplate(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 log playback
PROBLEM DESCRIPTION:
Tivoli Performance Viewer Log playback hangs
RECOMMENDATION:
Apply this fix:
Tivoli Performance Viewer 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 innovation for
different components.
The fix for this APAR is currently targeted for inclusion in cumulative
fix V5.02.17.