Configure message delay detection
Message delay detection is disabled by default. By setting appropriate values in the Server Configuration dialog box, you can configure the message delay detection mechanism according to the individual needs of your managed environment. You can configure how to detect message delays by setting configuration values in the following namepaces:
- Message Delay Detection Measuring Node Name Resolution
- Message Delay Detection Measuring Complete Message Routing
The following table shows the values, which are the same in both namespaces used by the message delay detection mechanism. These values have to be defined separately for each of the two available mechanisms. The assigned configuration values however can differ between two mechanisms.
| Value Name | Possible Values | Default Value | Description |
|---|---|---|---|
|
Enable message delay detection measuring node name resolution Enable message delay detection measuring the complete message routing |
True, False | False | This value enables or disables message delay detection based on the time it takes to resolve a node name or the time it takes to route a message through the HPOM message flow. Set it to True to enable, set to False to disable. |
| Log file name | String | C:\Program Files\HP\ |
The fully qualified name of the log file. If the file does not exist, it will be created automatically. The directory where the file will be stored must already exist. All new entries are appended at the end of the file. (Make sure sufficient disk space is available.) You can use the same log file for measuring both node name resolution and message routing. |
| Measuring type | NORMAL, CRITICAL | NORMAL |
A NORMAL measure waits until the measure interval has finished, then compares the elapsed time with the threshold and generates log information if the threshold has been exceeded. Only one single log entry is created per measure interval. This is the recommended measure type. A CRITICAL measure immediately generates log information as soon as the threshold value has been exceeded and does not wait until the end of the measure interval. It generates two log entries: the first one when the threshold has been exceeded and a second one when the measure interval has finished. If the second log entry is missing, then this indicates a hang during the measure interval. However the first entry contains sufficient information for finding out which message caused the hang. CRITICAL measures should only be used for tracking down hangs while routing messages and the threshold value should be set to a high value (more than 60000 milliseconds). |
| Threshold value (in milliseconds) | Integer | Node name resolution: 100 Message routing: 500 |
The threshold value in milliseconds. If the
threshold is exceeded then appropriate log records will be written
to the log output file.
Recommended values: |
Related Topics: