PQ58772: PERFORMANCE BOTTLENECK IN JCA IMPLEMENTATION | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description The WebSphere Application Server JCA implementation performs poorly because an excessive amount of time is spent executing string manipulation code. Analysis tracks the problem down to the com.ibm.connector2.poolmanager.PoolManager's toString method. The string manipulation appears to occur for tracing purposes, but that manipulation occurs regardless of whether tracing is enabled. Performance may be improved by restricting this code path from execution unless tracing on the component is enabled.Local fix There is no workaround available.Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server JCA users * **************************************************************** * PROBLEM DESCRIPTION: JCA had slow performance * **************************************************************** * RECOMMENDATION: * **************************************************************** The Pool Manager reserve() call was allocating resources that are used for trace even when trace was not active.Problem conclusion A fix was received from a Toronto tooling group, which made the performance better.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58772
IBM Group: Software Group
Modified date: Apr 1, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.