PQ77007: BBON1017E SERVER INSTANCE COULD NOT BE STOPPED MESSAGE AFTER WAITING A MAXIMUM OF 120 SECONDS WHICH WAS NOT ENOUGH TIME. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description WebSphere, while trying to recycle the server, issues a stop and waits the max of 120 seconds, but the server has not stopped by then. WebSphere thinks this is a problem and flags an error, discontinuing the recyle process for that server. It sometimes takes longer to bring down a server in this customer's environment, so they want the hard-coded 120 second maximum to be configurable.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: There is a hard-coded maximum amount of * * time - 120 seconds - System Management * * (SM) will wait for a server to stop * * during conversationactivation. The * * The hardcoded max is not long enough * * for some customer environments. * **************************************************************** * RECOMMENDATION: * **************************************************************** During conversation activation, when SM needs to recycle an active server, SM currently waits up to 120 seconds for a server to stop (after the stop command is issued). The maximum wait time of 120 seconds is hardcoded. If the server does not stop within the 120-second interval, SM considers the server "hung" and gives up trying to recycle that server. This maximum wait time is not long enough in some customer environments, forcing the customer to manually restart any servers erroneously thought by SM to be hung.Problem conclusion A configurable timer - specified using a new System Management environment variable - will be added in place of the existing hard-coded 120-second timer, allowing the user to specify a wait limit when servers are stopped and restarted during conversation activation. The new environment variable, MAX_SERVER_RECYCLE_WAIT, will have meaning only for the SM server and will default to 120, so the default behavior will be the same as it always has been. The following publications were revised as a result of APAR PQ77007: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling Java 2 Platform, Enterprise Edition (J2EE) Applications SA22-7836-05 and WebSphere Application Server V4.0.1 for z/OS and OS/390 Installation and Customization GA22-7834-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: www.ibm.com/software/webservers/appserv/zos_os390/library.html ________________________________________________________________ Appendix A. Environment Files Table 23 has been updated to indicate that the new MAX_SERVER_RECYCLE_WAIT environment variable applies to the SM server instance and is optional. The following description of the new enviroment variable has been added to the section "Environment variable descriptions:" MAX_SERVER_RECYCLE_WAIT=n Specifies a maximum time, in seconds, that the System Management (SM) server will wait for an application server to stop or restart during a server recycle operation. When a new conversation is activated, SM recycles active application servers whose configurations have changed in the new conversation. This recycle operation consists of stopping the server, copying the new configuration data into the active HFS directory, and restarting the server. SM will wait a maximum of MAX_SERVER_RECYCLE_WAIT seconds for the server stop and server start operations to complete. If either operation does not complete within this limit, SM will write an error message to the operator console and will not continue recycling the server. Note: MAX_SERVER_RECYCLE_WAIT is only used by the System Management server. If specified on any other server, it is ignored. Default: 120 Minimum value: 10 Maximum value: 3600 Example: MAX_SERVER_RECYCLE_WAIT=200 APAR PQ77007 is associated with SERVICE LEVEL W401600 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 #: PQ77007
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.