PQ66600: WAS 4.0+ PERFORMANCE DEGRADATION ON JNDI NAME NOT FOUND EXCEPTIONS. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description JNDI lookup method is very expensive. It spends excesive time in the return path via the "name not found" exception handler. . A stack trace is logged on every name not found exception. Logging the stack trace should only happen if trace is enabled.Local fix Problem summary **************************************************************** * USERS AFFECTED: Users who have WebSphere Application Server * * Release 4.0.1, 4.0.2, or 4.0.3 installed * * may affected by this problem. The problem * * is fixed in the release 4.0.4. * **************************************************************** * PROBLEM DESCRIPTION: A JDNI lookup method takes excessive * * time to return in the case of name * * not found. * **************************************************************** * RECOMMENDATION: * **************************************************************** The stack trace is logged on every NameNotFoundException. As a result, time spent on the lookup is longer than expected in the case of name not found.Problem conclusion For each NameNotFoundException, the stack trace is logged only when the trace is enabled.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 #: PQ66600
IBM Group: Software Group
Modified date: Sep 30, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.