+

Search Tips   |   Advanced Search

Excessive request timeout health policy target timeout value

The excessive request timeout health policy specifies an acceptable percentage of requests that can time out after being routed from the on demand router (ODR). For each control cycle of the health controller, the number of requests that time out after being routed from the ODR is examined. If the percentage of timed out requests exceeds the configured percentage, runtime tasks are generated to correct the situation.

If we enabled Intelligent Management for the web server, the timeout value is determined using the read/write timeout in the web server plug-in cluster properties (serverIOTimeout in the plugin-cfg.xml file). The health policy calculates the percentage of timeouts over a 60-second interval.

By default, the target timeout value for requests is 60 seconds. The default value for the percentage of requests that can time out in the excessive request timeout health policy is 5%. However, setting other properties in the environment can affect the target timeout value used.


Settings that affect the timeout value

The following settings in the console affect the target timeout value:


Determine the target timeout value

Depending the configuration, the timeout value used as target value for the excessive request timeout health policy can vary. The following decision tree helps you determine the target timeout value for ythe environment. The default setting is the path indicated with red arrows, or a target timeout value of 60 seconds, which is the default setting for the ODR outbound request timeout.

Figure 1. Target timeout value decision tree.

The settings that affect the target timeout value combine together to indicate the target timeout value.


Related

Health management
Create health policies
Manage runtime tasks
Intelligent Management: autonomic request flow manager custom properties