PK49888: DOCUMENT RAS TIMEOUT IMPROVEMENTS | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Document RAS timeout improvementsLocal fix Document RAS timeout improvementsProblem summary **************************************************************** * USERS AFFECTED: All users of Websphere Application Server * * V6.1.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: When a timeout occurs it is difficult * * to easily gather documentation * * sufficient to debug the timeout. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a timeout occurs the only option is to allow an SVCDUMP to be taken for the abend. An option to take a smaller java core dump has less impact on the system. A message indicating which task in the servant timed out would enable easier identification of the callstack to examine.Problem conclusion An option to take a javacore dump when certain timeout conditions occur was added and a new message indicates the TCB address of the thread that timed out. APAR PK49888 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/library A change to the z/OS version of the WebSphere Application Server Version 6.1 Information Center will be made available in August, 2007. The following new custom properties will be added to the topic "Application server z/OS custom properties:" control_region_http_queue_timeout_percent Specifies the percentage of the HTTP dispatch time limit that should be used as the maximum amount of time that a request can spend on the workload management (WLM) queue. The protocol_http_timeout_output custom property is used to specify the maximum amount of time an HTTP request can wait to be dispatched before an error message is issued that indicates that an HTTP dispatch timeout has occurred. Data Type Integer Range 0 - 99 Default 0 control_region_https_queue_timeout_percent Specifies the percentage of the HTTPS dispatch time limit that should be used as the maximum amount of time that a request can spend on the workload management (WLM) queue. The protocol_https_timeout_output custom property is used to specify the maximum amount of time an HTTPS request can wait to be dispatched before an error message is issued that indicates that an HTTPS dispatch timeout has occurred. Data Type Integer Range 0 - 99 Default 0 control_region_iiop_queue_timeout_percent Specifies the percentage of the IIOP dispatch time limit that should be used as the maximum amount of time that an IIOP request can spend on the workload management (WLM) queue. The control_region_wlm_dispatch_timeout custom property is used to specify the maximum amount of time an IIOP request can wait to be dispatched before an error message is issued that indicates that an IIOP dispatch timeout has occurred. Data Type Integer Range 0 - 99 Default 0 control_region_mdb_queue_timeout_percent Specifies the percentage of the MDB dispatch time limit that should be used as the maximum amount of time that an MDB request can spend on the workload management (WLM) queue. The control_region_mdb_request_timeout custom property is used to specify the maximum amount of time an MDB request can wait to be dispatched before an error message is issued that indicates that an MDB dispatch timeout has occurred. Data Type Integer Range 0 - 99 Default 0 control_region_sip_queue_timeout_percent Specifies the percentage of the SIP dispatch time limit that should be used as the maximum amount of time that a SIP request can spend on the workload management (WLM) queue. The protocol_sip_timeout_output custom property is used to specify the maximum amount of time a SIP request can wait to be dispatched before an error message is issued that indicates that a SIP dispatch timeout has occurred. Data Type Integer Range 0 - 99 Default 0 control_region_sips_queue_timeout_percent Specifies the percentage of the SIP SSL dispatch time limit that should be used as the maximum amount of time that a SIP SSL request can spend on the workload management (WLM) queue. The protocol_sips_timeout_output custom property is used to specify the maximum amount of time a SIPS request can wait to be dispatched before an error message is issued that indicates that a SIP dispatch timeout has occurred. Data Type Integer Range 0 - 99 Default 0 control_region_timeout_save_last_servant When set to 1, indicates that, if the value specified for the wlm_minimumSRCount property is greater than 1, the last available servant should not be abended because of a timeout situation until a new servant has been initialized. This property is ignored if the wlm_dynapplenv_single_server property is set to 1. Preventing the last available servant from abending even if a timeout situation has occurred enables other work to proceed until a new servant is initialized. However, preventing the last available servant from abending might result in a loss of system resources if the dispatched servant thread that encountered the timeout situation continues to loop or stops functioning. For example, if timeouts keep occurring, the system could use up a lot of the available servant threads. Data Type Boolean Default 0 control_region_timeout_dump_action Specifies the type of dump that should be taken whenever a timeout occurs for work that has been dispatched to a servant. This property only applies if the control_region_timeout_delay custom property is set to a non-zero value. Set this property to either JAVACORE or javacore, if you want a Java core dump, or set the property to either SVCDUMP, or svcdump if you want an SVC dump. Data Type String Default None control_region_timeout_dump_action_session Specifies the type of dump that should be taken whenever a timeout occurs for an HTTP, HTTPS, SIP, or SIPS request that has been dispatched to a servant. This property only applies if the corresponding variable, protocol_http_timeout_output_recovery, protocol_https_timeout_output_recovery, protocol_sip_timeout_output_recovery, or protocol_sips_timeout_output_recovery, is set to SESSION. The value specified for this property determines whether a Java core dump or an SVC dump is taken. Set this property to either JAVACORE or javacore, if you want a Java core dump, or set the property to either SVCDUMP, or svcdump if you want an SVC dump. Data Type String Default None protocol_accept_iiop_work_after_min_srs Specifies whether or not the application server waits for a minimum number of servants to be ready to accept work before the application server starts the IIOP transport channels. If this property is set to 1, when the minimum number of servants is ready for work, the IIOP transport channels starts accepting work. If this property is set to 0, the IIOP transport channels start when the controller starts. When this property is set to true, the value specified for the Minimum Number of Instances property determines the number of servants that must be ready before the IIOP transport channels start. To change the setting of the Minimum Number of Instances property for an application server, in the administrative console, click Application servers > server > Java and Process Management > Server Instance. To change the setting of this property for a deployment manager, in the administrative console, click System administration > Deployment manager > Java and Process Management > Server Instance. Data Type Boolean Default 0 Used by Daemon No References to these new properties will be added to the topics "Timer overview," "Timeout Values - Controlling Behavior" and "Changing the values of variables references in BBOM0001I message." The following information will be added to the topic "Modify command:" The following information will be added under "Parameters" and these new parameters will be added to the "Getting help for the modify command" example. TIMEOUTDUMPACTION=n Specifies that a dump should be taken when a timeout occurs for work that has been dispatched to a servant and control_region_timeout_delay is non-zero. The valid values are JAVACORE, javacore, SVCDUMP, svcdump, NONE, or none. TIMEOUTDUMPACTIONSESSION=n Specifies that a dump should be taken when a timeout occurs for an HTTP, HTTPS, SIP, or SIPS request that has been dispatched to a servant and the corresponding environment variable protocol_http_timeout_output_recovery, protocol_https_timeout_output_recovery, protocol_sip_timeout_output_recovery, or protocol_sips_timeout_output_recovery is set to SESSION. The valid values are JAVACORE, javacore, SVCDUMP, or svcdump, NONE, or none. APAR PK49888 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.11 of WebSphere Application Server V6.1 for z/OS.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 Publications Referenced
|
Document Information |
Current web document: swg1PK49888.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK49888
IBM Group: Software Group
Modified date: Oct 2, 2007
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.