PQ59932: TRY/FINALLY BLOCKS FOR JSP CUSTOM TAGS ARE CAUSING PERFORMANCE PROBLEMS DURING GARBAGE COLLECTION USING SOLARIS JDK 1.3.0/1.3.1 | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The problem appears to be that the JVM classloader handles nested blocks. Factors that affect the bug are: 1)How deeply nested the blocks are. 2)The number of try/catch blocks. 3)The complexity of the try/catch blocks. The memory usage is exponential. Garbage collection also appears to be effected. When the blocks were flattened out the GC times went away.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server developers * * using custom tags and jsp's. * **************************************************************** * PROBLEM DESCRIPTION: Performance problem when jsp contains * * nested custom tags. * **************************************************************** * RECOMMENDATION: * **************************************************************** Java Garbage Collection time increases exponentially with each try/finally block on a page causing slow response times.Problem conclusion Removed try/finally blocks for each custom tag to get around JDK performance problem.Temporary fix //wasdoc0/apars/pq59932/4.0.2Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ59932
IBM Group: Software Group
Modified date: Apr 11, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.