PQ69571: COMMANDEXCEPTION PERFORMANCE PROBLEM

 Fixes are available

PQ69571; 5.0: Performance problem in DistributedException class
5.0.1: WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1)
5.0.1: WebSphere Application Server Enterprise Edition Version 5.0 Fix Pack 1



APAR status
Closed as program error.

Error description
The Websphere DistributedException class utilized too much CPU
when creating an exception.  The extra CPU utilization was
caused by the class retrieving the exception back trace for
serialization purposes.  The corrected code now defers
retrieiving the exception backtrace until the exception is
serialized.  So, if no serialization occurs, a large
performance increase is observed when utilization the
DistributedException class and its subclasses.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Users of        *
*                 Command Exception                            *
****************************************************************
* PROBLEM DESCRIPTION: The Websphere DistributedException      *
*                      class utilized too much CPU when        *
*                      creating an exception.  The extra CPU   *
*                      utilization was caused by the class     *
*                      retrieving the exception back trace     *
*                      for serialization purposes.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Websphere DistributedException class utilized too much CPU
when creating an exception.  The extra CPU utilization was
caused by the class retrieving the exception back trace for
serialization purposes.  The corrected code now defers
retrieiving the exception backtrace until the exception is
serialized.  So, if no serialization occurs, a large
performance increase is observed when utilization the
DistributedException class and its subclasses.
Problem conclusion
The corrected code now defers retrieiving the exception
backtrace until the exception is serialized.  So,
if no serialization occurs, a large performance increase is
observed when utilization the DistributedException
class and its subclasses.
Temporary fix Comments
APAR information
APAR number PQ69571
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-01-07
Closed date 2003-01-21
Last modified date 2003-01-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
RUNTIME          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ69571
IBM Group: Software Group
Modified date: Jan 21, 2003