PQ83516: C9C21277 and ABEND0C4 when recycle 1 of 2 server instances under same server definition with RECYCLE_J2EE_SERVERS=NO | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer has created 2 server instances WAOBS1A and WAOBS1B of the server WAOBS1, created JCL for each server instance and starts them with /S WAOBS1A resp /S WAOBS1B. This works OK. Customer first used RECYCLE_J2EE_SERVERS=YES for the Systems management to activate automatical recycling when deploying new application. This worked OK. Then changed to RECYCLE_J2EE_SERVERS=NO and got this problem: After new application has been deployed customer first restarts WAOBS1B, the naming registration is done, but the message 'BBOU0695I NAMING REGISTRATION COMPLETED FOR SERVER WAOBS1' is shown on the wrong server WAOBS1A and this server goes down, first with an error code C9C21277 and once also followed by ABEND0C4. WAOB1SB comes up OK. Recreate showed that during restart of the instance, the signal meant to notify the control region that naming registration was complete was misdirected to the other, active, instance of the server. The instance which should have been notified never was. the SM server region send an outbound request to the control region METHOD=endOfJNDIRegistration. This is sent to the wrong ASID, based on the wrong instance being notified of the naming registration completion.Local fix when RECYCLE_J2EE_SERVERS=YES , automatic recycling when deploying a new application works as expected. This problem only seems to occure when RECYCLE_J2EE_SERVERS=NOProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: C9C21277 and ABEND0C4 when recycle 1 * * of 2 server instances under same server * * definition with RECYCLE_J2EE_SERVERS=NO * **************************************************************** * RECOMMENDATION: * **************************************************************** When RECYCLE_J2EE_SERVERS=N is specified, SM does not automatically recycle J2EE servers during activation of a new conversation. It is up to the operator to stop and restart these server instances manually. If a server has multiple active server instances under these conditions, and an operator stops and restarts one of them, problems occur with naming registration for the restarted instance. An exception with minor code C9C21277 may result, the restarted instance may not successfully restart, and the other instance - the one that is still active - may abend. Problem was caused by misdirecting the endOfJNDIRegistration() processing to the wrong server instance, that is, to the instance that remained active rather than to the instance that was being restarted.Problem conclusion The problem was caused by SM driving the endOfJNDIRegistration method on the generic server object and not the specific server object, since the generic server name was the only parameter passed into the registerHomes method. The changed code now passes an additional parameter, specificServerName, to the registerHomes method, and this specific server name is used to build the systems management object (SMO) on which the endOfJNDIRegistration method is driven. APAR PQ83516 is associated with SERVICE LEVEL W401609 of WebSphere Application Server version 4.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: 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 #: PQ83516
IBM Group: Software Group
Modified date: Mar 3, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.