Autonomic request flow manager cell-wide custom properties

Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS

Autonomic request flow manager cell-wide custom properties

You can use these cell-wide custom properties to configure memory overload protection.

Configure cell-wide custom properties for memory overload protection

Unless otherwise specified, create these custom properties on the cell using the following steps. From the administrative console:

Expand System administration > Cell > Custom properties > New.
Type the name of the custom property. See following information for specifying the value.
Click Apply and save your changes.

Table 1. Custom properties for configuring memory overload protection

Name Cell location Default Description

MOP.AveragingWindowInMS
Application server

180000

The averaging window in milliseconds used by memory overload protection. This time interval should be at least as long as the lifetime of 95% of the HTTP sessions, SIP dialogs, and application sessions. If the time interval is too short, MOP may not protect against memory overload. If the time interval is much longer than the lifetime of these objects, MOP will still protect against memory overload but it will take MOP longer to ramp up to learn the maximum rate.
MOP.InitialMaxRatePerSec
Application server

1

If there is no persisted maximum rate value, this value is used as the initial maximum rate.
AC5.BurstFactor
On demand router (ODR)

3

This value affects how tolerant MOP is to bursts of traffic. If the maximum rate is 1 per second and the burst factor is 1, then one unit of non-affinity traffic is admitted if it did not admit one in the last second. If the burst factor is 3 however, it admits 3 every 3 seconds.

Related concepts

Memory overload protection

Related tasks

Configure the autonomic request flow manager
Autonomic request flow manager advanced custom properties

Name	Cell location	Default	Description
MOP.AveragingWindowInMS	Application server	180000	The averaging window in milliseconds used by memory overload protection. This time interval should be at least as long as the lifetime of 95% of the HTTP sessions, SIP dialogs, and application sessions. If the time interval is too short, MOP may not protect against memory overload. If the time interval is much longer than the lifetime of these objects, MOP will still protect against memory overload but it will take MOP longer to ramp up to learn the maximum rate.
MOP.InitialMaxRatePerSec	Application server	1	If there is no persisted maximum rate value, this value is used as the initial maximum rate.
AC5.BurstFactor	On demand router (ODR)	3	This value affects how tolerant MOP is to bursts of traffic. If the maximum rate is 1 per second and the burst factor is 1, then one unit of non-affinity traffic is admitted if it did not admit one in the last second. If the burst factor is 3 however, it admits 3 every 3 seconds.