The Request Manager Automatic Recycle feature starts a new instance of the Request Manager when the current instance has processed a specified number of requests or has been running for a specified period of time. You can determine the appropriate threshold by analyzing when and why performance deteriorates.
The Registry Server manages the recycling process. When the current instance of the Request Manager reaches its threshold, the Registry Server starts a new instance to process all new sessions while the current instance processes requests from the current sessions. When the current instance has finished processing requests, it shuts down (it may need to wait for existing sessions to be terminated or time out before shutting down). After a new instance has started, the Registry Server can force the current instance to shut down after a specified period of time if any users are still logged on or any sessions are hung. You can also configure the Registry Server to monitor unexpected terminations of the Request Manager. When the Registry Server detects that the Request Manager has terminated abnormally, it starts a new instance of the Request Manager.
The following sections provide configuration settings for the Request Manager Automatic Recycle feature. You must restart the Rational ClearQuest Server for changes made to the properties to take effect.
By default, the Request Manager Automatic Recycle feature is enabled. To disable it, set the ENABLE_RECYCLING property in the file, csm.properties to FALSE. The file is installed in, <INSTALLATION ROOT>\clearquest\cqweb\csm.properties. Note that by disabling it may jeopardize the reliability and availability of the Request Manager.
By default, the Request Manager is set to recycle everyday at 1:00 a.m. To disable the time-based recycling, comment out the property.
You can specify the format for a different interval in the TIME_CRITERIA property in the file rmmanager.properties: FREQUENCY|[HOURS][DAYS]|[TIME] .
Specify the FREQUENCY as HOURLY, DAILY, or EVERYFEWDAYS.
TIME_CRITERIA=HOURLY|2
The HOURLY interval must be greater than 1. However, if you need to recycle the Request Manager every hour, contact IBM Rational Customer Support.
TIME_CRITERIA=EVERYFEWDAYS|3|10:30 AM
The daily EVERYFEWDAYS interval must be greater or equal to 1 if you change the default.
TIME_CRITERIA=DAILY|1:00 AM
NUMBER_REQUEST_MANAGERS=2
To recycle the Request Manager after it processes a specified number of requests, set the NUMBER_OF_REQUESTS_CRITERIA property in the file, <INSTALLATION_ROOT>\clearquest\cqweb\cqserver\config\rmmanager.properties. By default, this property is disabled.
Examples:
2 instances of the Request Manager recycles after each has processed 500,000 requests.
NUMBER_REQUEST_MANAGERS=2
NUMBER_OF_REQUESTS_CRITERIA=500000
Only two instances of the Request Manager can exist at one time. On occasion, the current instance of the Request Manager may not shut down even after it reaches its threshold because users are logged in or sessions are hung. Because the first instance reaches its threshold, the second instance of the Request Manager does start to process new requests. However, when the second instance reaches its threshold, a new instance cannot start if the first instance is still running.
The order in which instances of the Request Manager start and shut down is sequential. Therefore, even if the second instance of the Request Manager reaches its designated threshold and has no active or hung user sessions, it cannot shut down until the first instance shuts down. By setting the ENABLE_FORCED_EXIT property to TRUE, the Registry Server forces the first instance to shut down when the second instance reaches its threshold. Once the first instance shuts down, the second can then shut down and a new instance can start and begin processing any new requests.
By default, ENABLE_FORCED_EXIT is set to TRUE. This property is in the file, csm.properties.
You can set the Registry Server to start a new instance of the Request Manager when it detects the current instance has crashed. Set the ENABLE_MONITORING_FOR_CRASHES property to TRUE in the file, csm.properties for this to occur. The default value for this property is, TRUE. If you set it to FALSE and the Request Manger crashes or exits, a new instance does not start. However, if you have Automatic Recycle disabled in the ENABLE_RECYCLING property, and you set ENABLE_MONITORING_FOR_CRASHES to TRUE, a new instance of the Request Manager will start up if the current one crashes.