PQ63711: WHEN THE CUSTOMER USES THE STOPMVS COMMAND ON THE CONTROL REGION ALL SESSIONS END IMMEDIATELY | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer is running HTTP Transport Handler configuration. Customer was running a stress tool against the server and issued a stop on the control region. There are many sessions where the stress tool successfully connected and wrote the request, but an attempt to read the response failed before any data was returned and there is no "Connection: close" header as expected. In addition, whenever a second control region is started (first one still running) there is a one minute delay (can be seen as absolutely no tracepoints in the logs for a minute also) and the CPU drops from about 90% to 20% during this second control region startup. Customer would like this APAR to address both the start and stop issues he is experiencing during start and stop listening for HTTP work.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: HTTP Transport and HTTP SSL work needs * * better controls during initalization * * and termination of Server regions. * **************************************************************** * RECOMMENDATION: * **************************************************************** Better control of when inbound HTTP work is accepted into the Server is needed. Currently, the HTTP Transport and HTTP SSL listeners are started before any Server Regions are available to handle the work. This may lead to delays in processing the HTTP work as well as timeouts, and thus, failure of the HTTP work. Also, during termination, new HTTP connections need to be avoided to allow an orderly "stop" of the Server.Problem conclusion To control when inbound HTTP work is accepted into the Application Server, a new environment variable called BBOO_ACCEPT_HTTP_WORK_AFTER_MIN_SRS is being introduced: The following publications have been revised as a result of APAR PQ63711: ________________________________________________________________ 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/ ________________________________________________________________ Chapter 14, pg. 313 (new message) C9C2127C Explanation: IBM Internal Only User Response: Contact the IBM SUpport Center. ________________________________________________________________ Chapter 14, pg. 313 (new message) C9C2127D Explanation: IBM Internal Only User Response: Contact the IBM SUpport Center. ________________________________________________________________ Chapter 14, pg. 404 (new message) C9C2E436 Explanation: The minor code indicates an out of memory condition when a WebSphere module attempted to allocate storage. User Response: See minor code C9C2E001. ________________________________________________________________ ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 Installation and Customization GA22-7834-05 ________________________________________________________________ Appendix A, pg. 368 (new information) |--------------------------------------------------------------| |Environment variable=<default> | ... |Business | ... | | | ... |application| | | | ... |server | | | | ... |instance | | |--------------------------------------------------------------| |BBOO_ACCEPT_HTTP_WORK_AFTER_N_ | |O | | |SECS=<pv>n</pv> | | | | |--------------------------------------------------------------| |BBOO_ACCEPT_HTTP_WORK_AFTER_N_ | |O | | |SRS=<pv>n</pv> | | | | |--------------------------------------------------------------| ________________________________________________________________ Appendix A, pg. 380 (new information) BBOO_ACCEPT_HTTP_WORK_AFTER_N_SECS=n Defines the amount of time, specified in seconds, to wait for the desired number of server regions as defined by environment variable BBOO_ACCEPT_HTTP_WORK_AFTER_N_SRS before accepting work over the HTTP Transport or HTTP SSL protocols. The default is 300 seconds and the minimum value is 10 seconds. Example:BBOO_ACCEPT_HTTP_WORK_AFTER_N_SECS=300 BBOO_ACCEPT_HTTP_WORK_AFTER_N_SRS=n Defines the number of server regions that must be ready for work before HTTP work is accepted into the server. Once the specified number of server regions are ready, the HTTP Transport and HTTP SSL protocols start accepting work. Both the default and the minimum value are 1. Example:BBOO_ACCEPT_HTTP_WORK_AFTER_N_SRS=1 ________________________________________________________________ BBOO_ACCEPT_HTTP_WORK_AFTER_MIN_SRS Default: 0 Description: Indicates that the minimum number of Server Regions must be ready for work before HTTP work will be accepted into the Server. The minimum number of Server Regions is specified on the MIN_SRS environment variable. Once the minimum number of Server Regions are ready for work the HTTP Transport and HTTP SSL protocols will start accepting work. To avoid accepting new HTTP connections when the Server is stopping code has been added to cancel the Asynchronous I/O and close the socket related to the HTTP protocols much earlier in STOP processing. APAR PQ63711 is associated with SERVICE LEVEL W401402 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: UQ70733 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 #: PQ63711
IBM Group: Software Group
Modified date: Nov 3, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.