PQ66553: SERVER REGION ABENDS WITH SDC3 RSN=04010001 WHEN STARTING UP IF THE CONTROL REGION IS BEING STOPPED. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description If WLM starts a new server region during the period of time when while the control region is stopping, the server region ABENDs with SDC3 reason code=04010001. WLM will try to start the server region 3 times, but each one will fail due to SDC3. At this point WLM deactivates the application environment for the server. The operator must manually restart the WLM application environment before new server regions will start up. . This APAR will also address the problem where during normal processing of a stop command issued to the application server control region (CR), the CR comes down before the application server server region (SR). As one of the last things during SR termination, it tries to communicate to the CR but the CR is already down, thus producing the following abend symptoms in the SR. . In the application server server region job output you will see: CEE0374C CONDITION = CEE3250C where CEE3250C indicates another abend, in this case a 0D6. . In the WebSphere error log and/or in the exception tracing of the application server server region (will be in sysprint if TRACEBUFFLOC=SYSPRINT or in ctrace output if TRACEBUFFLOC=BUFFER), you will see abend0D6: BBOU0036W Processing for signal 'SIGABND'(18) with abend=000D6000 rsncode=00000022 si_code='ABND_REAL'(170) si_errno=0 si_addr=00000000 , in current thread . followed by: BBOU0565W An 0D6 Abend occurred. The target PC is no longer valid. BBOU0038W TERMINATING THE CURRENT PROCESS, REASON=C9C20008Local fix In the case of the abendDC3 reason code=04010001, the operator can manually reactivate the WLM application environment and restart the appserver.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: If WLM starts a new server region * * during the period of time when while * * the control region is stopping, the * * server region ABENDs with SDC3. * **************************************************************** * RECOMMENDATION: * **************************************************************** A Stop for the control region got issued, a tran timed-out and a server region got abended, WLM started another server region, BBOOBIND looks for his control region in the ASR but can not find it because he skips stopping CTL regions, BBOOBIND abends with abend code DC3 reason code 04010001, server region ends, WLM keeps starting server regions and the server regions keep ending until WLM stops the application environment. This APAR will also address the problem where during normal processing of a stop command issued to the application server control region (CR), the CR comes down before the application server server region (SR). As one of the last things during SR termination, it tries to communicate to the CR but the CR is already down, thus producing the following abend symptoms in the SR. In the application server server region job output you will see: CEE0374C CONDITION = CEE3250C where CEE3250C indicates another abend, in this case a 0D6. In the WebSphere error log and/or in the exception tracing of the application server server region (will be in sysprint if TRACEBUFFLOC=SYSPRINT or in ctrace output if TRACEBUFFLOC=BUFFER), you will see abend0D6: BBOU0036W Processing for signal 'SIGABND'(18) with abend=000D6000 rsncode=00000022 si_code='ABND_REAL'(170) si_errno=0 si_addr=00000000 , in current thread followed by: BBOU0565W An 0D6 Abend occurred. The target PC is no longer valid. BBOU0038W TERMINATING THE CURRENT PROCESS, REASON=C9C20008Problem conclusion Module bboobind.plx has been updated to not set bbodasrr_search_skip_shutting_down when searching the asr. The following publication was revised as a result of APAR PQ66553: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Messages and Diagnosis GA22-7837-06 ________________________________________________________________ This APAR requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/zos_os390 /library.html ________________________________________________________________ Chapter 16, pg. 334 (new message) C9C2127E Explanation: Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed. User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center. ________________________________________________________________ Chapter 16, pg. 334 (new message) C9C2127F Explanation: ACRW request not queued because the server is being stopped. Control is returned to the requestor with this minor code to indicate that the request was not processed. User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center. ________________________________________________________________ Chapter 16, pg. 334 (new message) C9C21280 Explanation: Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed. User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM Support Center. ______________________________________________________________ Chapter 16, pg. 334 (new message) C9C21281 Explanation: Synchronous ACRW request not processed because the server is stopping. The requester is posted or released with this minor code to indicate that the request was not processed. User Response: None, if the error occurred in server region that was initializing when the control region was stopping. Otherwise report this error to your next level of support or to the IBM. ______________________________________________________________ APAR PQ66553 is associated with SERVICE LEVEL W401403 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: 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 #: PQ66553
IBM Group: Software Group
Modified date: Nov 3, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.