PQ57982: ABEND IN NAMING CONTROL REGION DURING SHUTDOWN. DUMP TITLE= COMPID=5655A9801,ISSUER=BBORMCDP,ERRNO=C9C20008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description ABEND in Naming Control region when shutting down WebSphere for z/OS. Customer issues a 'STOP DAEMON' command, normal shutdown occurs, Naming control region takes an SVC Dump, with the title COMPON=WEBSPHERE Z/OS,COMPID=5655A9801,ISSUER=BBORMCDP,ERRNO= C9C20008. Looking in the WebSphere Error Log, you see that a previous ABEND CC3 Reasoncode=0A070001 occurred in the NAMING Control Region.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0 for z/OS and OS/390. * * * * All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: ABEND CC3 reason code 0A070001 in * * NAMING control region during normal * * WebSphere shutdown. * **************************************************************** * RECOMMENDATION: * **************************************************************** NAMING control region tried to call the Daemon for ASR (Active Server Repository) services but was abended with an ABEND CC3 reason code 0A070001 because the Daemon was gone. This is a timing window. Error log had: BBOU0036W Processing for signal (18) with abend=00CC3000 rsncode=0A070001 followed by BBOU0038W TERMINATING THE CURRENT PROCESS REASON=C9C20008. Comm establishes a cleanup object under the Session Manager constructor. During normal termination, Stop processing drives stopAllListening. When the main thread ends, the cleanup object deletes the session manager which, in turn, drives stopAllListening again. In stopAllListening, we deregister from the ASR table. If you stop the Daemon, it stops all the other servers and waits for them to go away (disappear from the ASR), then it, too, goes down. Once the Daemon goes away, ASR services don't work anymore (they abend). Since nothing is done to keep the cleanup object from running again, we deregister once, which allows the Daemon to go away, then try to deregister again. Second flavor found during testing: Since reset method in bbodasrr.h did not clear the correct area, system management stop processing in deactivate_impl only really waits for one server to go down before it goes down the rest of the way.Problem conclusion Code has been modified to only call routine SessionManager::stopAllListening in module bbocsmgr.cpp once. Reset method in bbodasrr.h was changed to clear the correct area. APAR PQ57982 is associated with SERVICE LEVEL W400063 of WebSphere Application Server V4.0 for z/OS and OS/390. APAR PQ57982 is associated with SERVICE LEVEL W401034 of WebSphere Application Server V4.0.1 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: UQ64365 UQ64366 Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ57982
IBM Group: Software Group
Modified date: Apr 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.