You can use timeout properties to control the amount of time you allow for various requests to complete. Some of these properties map to internal variable names. The internal variable names are provided here to aid you with debugging.
For WebSphere® Application Server Version 7 and later, listener ports are deprecated. Therefore plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. However, do not begin this migration until you are sure that the application does not have to work on application servers earlier than WebSphere Application Server Version 7. In some cases, you continue to use the WebSphere MQ message-driven bean deployment and listener ports and in other case you use the WebSphere MQ message-driven bean deployment and activation specifications.
As you follow the instructions to configure these properties, remember what properties apply to listener ports versus activation specifications.
Default: 0
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container services > ORB service > z/OS® additional settings.
Default: 0
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container services > ORB service > z/OS additional settings.
Default: 300 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container services > ORB service > z/OS additional settings.
Internal variable name (for debugging purposes): Locate the internal variable name, control_region_wlm_dispatch_timeout, in the was.env file or the JES job log.
Example: WLM timeout=600
Use the control_region_iiop_queue_timeout_percent server custom property to designate a percentage of the WLM timeout as the amount of time a request can remain on the WLM queue.
Because the sysplex TCP/IP that runs through the coupling facility does not always tell the client when the other end of the socket has closed, clients can wait indefinitely for a response unless you set this property. Setting the Request timeout property ensures that the client gets a response within the specified time, even if the response is a COMM_FAILURE exception.
Default: 0 (unlimited). No timeout value is set.
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > > Container services > ORB service > z/OS additional settings.
If you use command-line scripting, the full name of this system property is com.ibm.CORBA.RequestTimeout.
Example: Specifying Request timeout=2, sets the time limit to 2 seconds.
Setting this value to 0 indicates that the timeout does not apply, and the value of the maximum transaction timeout is used instead.
Default: 120 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container services > Transaction service.
Internal variable name (for debugging purposes): Locate transaction_defaultTimeout in the was.env file or the JES job log file.
This value constrains the upper bound of all other timers. If an application uses the UserTransaction.setTransactionTimeout() method to specify a longer length of time, then the J2EE server changes the application setting to the value specified for the Maximum transaction timeout property.
Setting this value to 0 indicates that the timeout does not apply, and any transactions that are affected by this timeout never time out.
Default: 300 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Container services > Transaction service.
Internal variable name (for debugging purposes): Locate the internal variable name, transaction_maximumTimeout, in the was.env file or the JES job log.
If the operator replies that recovery is to continue, then the controller attempts recovery for the specified amount of time before reissuing the WTOR message. After all the transactions are resolved, the controller region terminates. This property applies only to controllers in peer restart and recovery mode.
Default: 15 minutes
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the transaction_recoveryTimeout property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate transaction_recoveryTimeout in the was.env file or the JES job log.
Example: transaction_recoveryTimeout=7
Default: 120
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the control_region_mdb_request_timeout property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate control_region_mdb_request_timeout in the was.env file or the JES job log. See the application server z/OS custom properties documentation for additional information.
Example: control_region_mdb_request_timeout=180
Use the control_region_mdb_queue_timeout_percent server custom property name to designate a percentage of the value specified for the control_region_mdb_request_timeout property as the amount of time that a MDB request can remain on the WLM queue. The control_region_mdb_request_timeout custom property specifies the combined amount of time that the request spends on the WLM queue and in dispatch. The control_region_mdb_queue_timeout_percent property only applies to the amount of time that the request spends on the WLM queue.
This property can be set to 0 or 1.
The setting for this property is ignored if the wlm_dynapplenv_single_server property is set to 1.
Default: 0
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the control_region_timeout_save_last_servant property in the Name field, and specify 1 in the Value field.
Internal variable name (for debugging purposes): Locate control_region_timeout_save_last_servant in the was.env file or the JES job log.
Default: SERVANT
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the protocol_http_timeout_output_recovery property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate protocol_http_timeout_output_recovery in the was.env file or the JES job log.
Example: protocol_http_timeout_output_recovery=SERVANT
Default: SERVANT
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the protocol_https_timeout_output_recovery property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate protocol_https_timeout_output_recovery in the was.env file or the JES job log.
Example: protocol_https_timeout_output_recovery=SESSION
Default: 120
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the protocol_sip_timeout_output custom property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate protocol_sip_timeout_output in the was.env file or the JES job log.
Example: protocol_sip_timeout_output=180
Use the control_region_sip_queue_timeout_percent server custom property name to designate a percentage of the value specified for the protocol_sip_timeout_output property as the amount of time a request can remain on the WLM queue.
Default: 120
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the protocol_sips_timeout_output custom property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate protocol_sips_timeout_output in the was.env file or the JES job log. for additional information.
Example: protocol_sips_timeout_output=180
Use the control_region_sips_queue_timeout_percent server custom property name to designate a percentage of the value specified for the protocol_sips_timeout_output property as the amount of time a request can remain on the WLM queue.
Default: SERVANT
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the protocol_sip_timeout_output_recovery property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate protocol_sip_timeout_output_recovery in the was.env file or the JES job log.
Example: protocol_sip_timeout_output_recovery=SERVANT
Default: SERVANT
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the protocol_sips_timeout_output_recovery property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate protocol_sips_timeout_output_recovery in the was.env file or the JES job log.
Example: protocol_sips_timeout_output_recovery=SERVANT
This property helps prevent a single application request from monopolizing the available CPU time because it allows you to limit the amount of CPU time that a single request can use. A CPU monitor is invoked when a request is dispatched. If the request exceeds the specified amount of CPU time, the controller considers the request unresponsive. The controller then issues message BBOO0327, to let the requesting application know that the request was unresponsive.
The monitor, that monitors the amount of CPU time that a request is using, typically sends a signal to the dispatched thread when the amount of CPU time used exceeds the specified amount. However, there are situations when this signal cannot be delivered, and the request remains pending. For example, if the thread goes native and invokes a PC routine, the signal remains pending until the PC routine returns.
After the signal is delivered on the dispatch thread, the WLM enclave, that is associated with the dispatched request, is quiesced. This situation lowers the dispatch priority of this request, and this request should now only get CPU resources when the system is experiencing a light work load.
Default: 0
How to specify: To specify this property, in the administrative console, click Environment > WebSphere variables, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the server_region_stalled_thread_threshold_percent property in the Name field, and specify a different value in the Value field.
Internal variable name (for debugging purposes): Locate server_region_stalled_thread_threshold_percent in the was.env file or the JES job log.
Example: server_region_stalled_thread_threshold_percent=5
The following 2 JVM properties can be set by clicking Application Servers -> <SERVER> -> Process Definition -> Servant -> Java Virtual Machine -> Custom Properties.
Data Type: Boolean
Default: 0
Used by Daemon: No. Only applicable to servant regions.
Data Type: Boolean
Default: 0
Used by Daemon: No. Only applicable to servant regions.
Default: 100
How to specify: To specify this property, in the administrative console, click Security > SSL application servers > New SSL repertoire
Locate these internal variables in the was.env file or the JES job log.
Default: 0 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Web container transport chains > TCP inbound channel.
Default: 120 seconds
How to specify: To specify this property, in the administrative console, click
server_name, and then, under Web Container Settings, click .Internal variable name (for debugging purposes): If you are debugging a problem in SSL-enabled transport, then locate the internal variable name, protocol_https_timeout_output, in the was.env file or the JES job log. If you are debugging a problem in non-SSL transport, then locate the internal variable name, protocol_http_timeout_output, in the was.env file or the JES job log.
Use the control_region_http_queue_timeout_percent and control_region_https_queue_timeout_percent server custom properties to designate a percentage of the ConnectionResponseTimeout property as the amount of time that a request can remain on the WLM queue.
Default: 30 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name, and then, under Web Container Settings, click Web container transport chains > chain_name > HTTP inbound channel.
Default: 60 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name, and then, under Web Container Settings, click Web container transport chains > chain_name > HTTP inbound channel.
Default: 60 seconds
How to specify: To specify this property, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name, and then, under Web Container Settings, click Web container transport chains > chain_name > HTTP inbound channel.
Default: 10 seconds
How to specify: To specify this property, in the administrative console, click
server_name, and then, under Web Container Settings, click .Default: 120 seconds
How to specify: To specify this property, in the administrative console, click
server_name, and then, under Web Container Settings, click .Internal variable name (for debugging purposes): If you are debugging a problem in SSL-enabled transport, then locate the internal variable name, protocol_https_timeout_output, in the was.env file or the JES job log. If you are debugging a problem in non-SSL transport, then locate the internal variable name, protocol_http_timeout_output, in the was.env file or the JES job log.
Use the control_region_http_queue_timeout_percent and control_region_https_queue_timeout_percent server custom properties to designate a percentage of the ConnectionResponseTimeout property as the amount of time that a request can remain on the WLM queue.
Default: 30 seconds
How to specify: To specify this property, in the administrative console, click
server_name, and then, under Web Container Settings, click .