PQ52309: RECEIVE C9C21440 TRYING TO CREATE NEW CONVERSATION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The customer had recently deployed a very large and complex J2EE application. His attempt to create a new conversation using the Systems Management Administration EUI failed with a minor code of C9C21440. This minor code did not offer details of the failure, but we did find it failed in the following block of code: // lookup class registration in table classReg = findClass(className); // is class registered? if (classReg) { // create object by calling factory function if (classReg->m_factory_function) // @P2A { obj= (classReg->m_factory_function)(); Old_instance_count = classReg->m_instance_count; The trace output showed the findclass was successful, but the attempt to run the factory on the object resulted in the obj variable being set to null. It turns out, the following LE trace showed the system was running out of storage: |_Ism_MethodDOImpl_create | |-->(124) malloc(25968) | | | |new | |<--(124) R15=00000000 ERRNO=0000| |0084............................| |................................| |........ | The customer is running with 2G of storage available. That should be plenty to create a new conversation. So there are two issues here. 1) Excessive amounts of storage are used while creating a new conversation. 2) No indication of out of memory was given to help debug this problem.Local fix Right now the only way around this is to cold start and minimize the size of applications deployed.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: Creating a new conversation leaks * * storage. * **************************************************************** * RECOMMENDATION: * **************************************************************** After deploying very large and complex J2EE application, creating a new conversation using the WebSphere for z/OS Administration Application (Systems Management EUI) failed with a minor code of C9C21440. This minor code did not offer details of the failure, but it turned out that the system was running out of storage.Problem conclusion Create conversation was reimplemented using DB2 insert/select support. This solution resolves the reported storage leak which occurred during create converstion processing. APAR PQ52309 is associated with SERVICE LEVEL W400047 of WebSphere Application Server V4.0 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ58662 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ52309
IBM Group: Software Group
Modified date: Nov 2, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.