Timeout variables let you control the amount of time you will allow for various requests to complete. Some of these variables map to internal variable names. The internal variable names are provided here to aid you with debugging.
ORB service advanced settings
Default: 0
How to specify: Specify this setting in the administrative console using the path Application Servers > server > ORB Service.
Internal variable name (for debugging purposes): Look for the internal variable name protocol_iiop_server_session_keepalive in the was.env file or the JES job log.
Default: 0
How to specify: Specify this custom property in the administrative console using the path Application Servers > server > ORB Service.
Internal variable name (for debugging purposes): Look for the internal variable name protocol_iiop_server_session_keepalive_ssl in the was.env file or the JES job log.
Note: This variable setting does not apply for HTTP requests or Scalable Messaging Support; for that type of work, the value specified through the ConnectionResponseTimeout variable controls the time allowed for dispatching work to a servant (region).
Default: 300 seconds
How to specify: Specify this setting in the administrative console using the path Application Servers > server > ORB Service.
Internal variable name (for debugging purposes): Look for the internal variable control_region_wlm_dispatch_timeout in the was.env file or the JES job log.
Example: WLM timeout=600
The value specified for this field is a server wide setting, that affects all outbound RMI/IIOP enterprise bean invocations that are made on this server.
The sysplex TCP/IP, that runs through the coupling facility, does not always tell the client when the other end of a socket is gone. Therefore, you should specify a value in the Request timeout field that ensures that the client gets a response within the specified time, even if the response is a COMM_FAILURE exception.
How to specify: Specify this custom property in the administrative console using the path Application Servers > server > ORB Service.
Internal variable name (for debugging purposes): Look for the internal variable protocol_iiop_local_timeout in the was.env file or the JES job log. The value that you see associated with this variable should be 10 times the value that you specified in the Request timeout field.
Example: Request timeout=2 sets the wait time to 2 seconds. The variable protocol_iiop_local_timeout=20 should appear in the was.env file.
Transaction service timeout variables
If the application transaction is not committed or rolled back within the specified time, the application transaction will be marked for roll-back and will be allowed to continue running for a grace period of about four minutes. If the application transaction is committed or rolled back during the grace period, the outcome of the transaction will always be rolled back. If the application transaction does not complete after the grace period, the controller abnormally ends the servant (region) in which the application component is running with ABEND EC3 RSN=04130002 or 04130005.
Note: Only the total transaction lifetime timeout and the maximum transaction timeout have grace periods.
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: Specify this setting in the administrative console using the path Application Servers > server > Container Services > Transaction Service.
Internal variable name (for debugging purposes): Look for the internal variable name transaction_defaultTimeout in the was.env file or the JES job log.
This value constrains the upper bound of all other timeouts. If an application assigns a greater amount of time through the UserTransaction.setTransactionTimeout() method, the J2EE server overrides the application setting to the value specified for the Maximum Transaction Timeout variable.
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: Specify this setting in the administrative console using the path Application Servers > server > Container Services > Transaction Service.
Internal variable name (for debugging purposes): Look for the internal variable name transaction_maximumTimeout in the was.env file or the JES job log.
If the operator replies that recovery should continue, the controller (region) will attempt recovery for the specified amount of time before re-issuing the WTOR message. Once all the transactions are resolved, the controller region terminates. This variable applies only to controllers in peer restart and recovery mode.
Default: 15 minutes
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Server infrastructure > Administration > Custom Properties > 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): The internal variable name is the same as the external variable name. Look for transaction_recoveryTimeout in the was.env file or the JES job log.
Example: transaction_recoveryTimeout=7
Server custom properties
Default: 120
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Server infrastructure > Administration > Custom Properties > 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): The internal variable name is the same as the external variable name. Look for control_region_mdb_request_timeout in the was.env file or the JES job log. See Configuring server custom properties for additional information.
Example: control_region_mdb_request_timeout=180
Default: SERVANT
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Server infrastructure > Administration > Custom Properties > 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): The internal variable name is the same as the external variable name. Look for 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: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Server infrastructure > Administration > Custom Properties > 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): The internal variable name is the same as the external variable name. Look for protocol_https_timeout_output_recovery in the was.env file or the JES job log.
Example: protocol_https_timeout_output_recovery=SESSION
TCP transport channel timeout properties
Note: The value specified for this property might be overridden by the wait times established for channels above this channel. For example, the wait time established for an HTTP transport channel overrides the value specified for the is property for every operation except the initial read on a new socket.
Default: 0 seconds
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Web Container Transport Chains > TCP Inbound Channel.
HTTP transport channel timeout properties
Default: 60 seconds
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Web Container Transport Chains > HTTP Inbound Channel.
Default: 60 seconds
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Web Container Transport Chains > HTTP Inbound Channel.
Default: 30 seconds
How to specify: Specify this custom property in the administrative console using the path Servers > Application Servers > server > Web Container Transport Chains > HTTP Inbound Channel.
HTTP Transport timeout variables
Default: 10 seconds
How to specify: Specify this custom property in the administrative console using the path Application Servers > server > Web Container > HTTP Transport>host>Custom Properties.
Note: This panel is only available if an HTTP transport is defined for your Application Server environment. If an HTTP transport is not defined for your environment, you can use the wsadmin scripting tool to define one. However, it is recommended that you use an HTTP transport channel instead of an HTTP transport whenever possible.
Internal variable name (for debugging purposes): If you are debugging a problem in SSL-enabled transport, look for the internal variable name protocol_https_timeout_input in the was.env file or the JES job log. If you are debugging a problem in non-SSL transport, look for the internal variable name protocol_http_timeout_input in the was.env file or the JES job log.
Default: 120 seconds
How to specify: Specify this custom property in the administrative console using the path Application Servers > server > Web Container > HTTP Transport > host> Custom Properties.
Internal variable name (for debugging purposes): If you are debugging a problem in SSL-enabled transport, look for 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, look for the internal variable name protocol_https_timeout_output in the was.env file or the JES job log.
Default: 30 seconds
How to specify: Specify this custom property in the administrative console using the path Application Servers > server > Web Container > HTTP Transport > host> Custom Properties.
Internal variable name (for debugging purposes): If you are debugging a problem in SSL-enabled transport, look for the internal variable name protocol_https_timeout_persistentSession in the was.env file or the JES job log. If you are debugging a problem in non-SSL transport, look for the internal variable name protocol_https_timeout_persistentSession in the was.env file or the JES job log.