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.
Default: 0
How to specify: To specify this property, in the administrative console, click 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 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 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 custom property, in the administrative console, click Application servers > server_name > > Container services > ORB service > z/OS additional settings.
Example: Specifying Request timeout=20, sets the time limit to 2 seconds.
Setting this value to zero 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 Application servers > server_name > Container services > Transaction service.
Internal variable name (for debugging purposes): Locate the internal variable name 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 zero 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 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 re-issuing the WTOR message. After all of 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. Then add the control_region_mdb_request_timeout property in the Name field, and specify an appropriate 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.
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 request can remain 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. Then add the control_region_timeout_save_last_servant property in the Name field, and specify an appropriate value 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. Then add the protocol_http_timeout_output_recovery property in the Name field, and specify an appropriate 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. Then add the protocol_http_timeout_output_recovery property in the Name field, and specify an appropriate 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 control_region_mdb_request_timeout 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 control_region_mdb_request_timeout 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.
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: 100
How to specify: To specify this property, in the administrative console, click Security > SSL Application servers > New SSL repertoire
Default: 100
How to specify: To specify this property, in the administrative console, click Security > SSL Application servers > New SSL repertoire
Default: 0 seconds
How to specify: To specify this property, in the administrative console, click Servers > Application servers > server_name > Web container Transport chains > TCP inbound channel.
Set this property for each of the HTTP transport channel definitions on the server. You must set this property for both SSL transport channels and non-SSL transport channels. If the response is not received within the specified length of time, then the servant might fail with ABEND EC3 and RSN=04130007. Setting this timer prevents client applications from waiting for a response from an application component that might be in a deadlock, looping, or encountering some other processing problem that causes the application component to stop processing requests.
Default: 300 seconds
How to specify: To specify this property, in the administrative console, click 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 a non-SSL transport channel, 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 application server custom properties to designate a percentage of the value specified for 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 > Application servers > server_name > Web container Transport chains > HTTP inbound channel.
Default: 60 seconds
How to specify: To specify this property, in the administrative console, click Servers > Application servers > server_name > Web container Transport chains > HTTP inbound channel.
Default: 60 seconds
How to specify: To specify this property, in the administrative console, click Servers > Application servers > server_name > Web container Transport chains > HTTP inbound channel.
Default: 10 seconds
Default: 120 seconds
How to specify: To specify this property, in the administrative console, click Application servers > server_name > Web container > Custom properties.
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 value specified for 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 Application servers > server_name > Web container > Custom properties.