PQ59556: APPSVR-THREADS WEBSPHERE APPLICATION SERVER V4.02 APPEARS TO HANG IN A CLASS LOADER DEADLOCK SITUATION (SEE SE04815) | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as unreproducible in next release. Error description Problem Description from APAR SE04815: After starting App server and logon to their first servlet (http://seiiicc1:42000/smc/SMCLogonSvt ) the application is then stuck and no CPU is consumed and they got no response from the Application Server. Threads appear 'stuck' in the class loader code (One in the WebSphere class loader, and one inside the JDK code) which result in that their application just hangs without any messages at all. This problem occure on regular basis after upgrading WAS from 4.01 to 4.02.Local fix Spoke with Lisa W. in AS/400 development. She already has code that has resolved customer problem on AS/400. This code will be delivered to Level 3 for review and repackaging. . A second option, as suggested by Brian M., is to package the rewritten classloader for 403 as an eFix.Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server Users * * currently on the 4.0.2 level of the * * application. * **************************************************************** * PROBLEM DESCRIPTION: After starting the application server * * and logging in to the first servlet, * * the application did not respond, no * * CPU is was consumed and there * * was no response from the application * * server. * * Threads appear 'stuck' in the class * * loader code and the JDK code. * * No error messages are seen. * **************************************************************** * RECOMMENDATION: * **************************************************************** After starting the application server and logging in to the first servlet, the application did not respond, no CPU is was consumed and there was no response from the application server. Threads appear 'stuck' in the class loader code and the JDK code. No error messages are seen. A rewrite of the classloader for 4.0.3 has taken care of this problem.Problem conclusion 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 #: PQ59556
IBM Group: Software Group
Modified date: Jan 10, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.