Explanation | Internal configuration error: the Filter chain of the HTTP Proxy does not include the MapRequest Filter from wlm.client. |
Action | Have IBM Services correct the error. |
Explanation | Code is unable to determine a hostname for the machine. |
Action | Make sure the machine has an IP address. |
Explanation | Internal error. |
Action | Report program defect to IBM. |
Explanation | The HTTP Proxy Filters that do Autonomic Request Flow Management have been initialized. |
Action | Informational message only, no action required. |
Explanation | Something unexpected went wrong. |
Action | Debug it. |
Explanation | Something unexpected went wrong earlier. |
Action | Find and debug it. |
Explanation | The SIP Proxy Filters that do Autonomic Request Flow Management have been initialized. |
Action | Informational message only, no action required. |
Explanation | The indicated response code is used when an HTTP message is rejected due to overload protection. |
Action | Informational message only; a different code can be configured by setting the http.overload.error custom property of the On-Demand Router. |
Explanation | The indicated response code is used when a SIP message is rejected due to overload protection. |
Action | Informational message only; different codes can be configured by setting the sip.overload.error and sipu.overload.error custom properties of the On-Demand Router. |
Explanation | Internal error. |
Action | Report program defect to IBM. |
Explanation | This is usually a consequence of a failure when construction of the ReqQMgr was attempted. |
Action | Find and debug the earlier failure. |
Explanation | Internal error. |
Action | Report program defect to IBM. |
Explanation | Internal error. |
Action | Report program defect to IBM. |
Explanation | Internal error. |
Action | Report program defect to IBM. |
Explanation | Internal error. |
Action | Report program defect to IBM. |
Explanation | ARFM was built with a table that tells whether to apply overload protection and queuing for each of several target operating systems, but a request arrived for a target not running an operating system in that table; ARFM will apply overload protection and queuing. |
Action | Report to IBM. |
Explanation | This should never happen. |
Action | Report to IBM. |
Explanation | Either something internal has failed or the cluster or node group is misconfigured. |
Action | If something internal has failed, report this to IBM; if something is misconfigured, fix it. |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | ARFM Gateways run only in On-Demand Router processes. |
Action | None. Informational entry. |
Explanation | The EnableFilters entry in arfm.cfg is false, which prevents registration of the ARFM filters; such disablement is intended to be used only by developers in performance investigations. |
Action | None. Informational entry. |
Explanation | Something went wrong in this ODR when ARFM tried to gain access to the ODC Tree. |
Action | Check the propagation mechanism. |
Explanation | Internal inconsistency. |
Action | Consult IBM. |
Explanation | This should not happen. |
Action | Report to IBM. |
Explanation | This information is read from the ODC Tree and used by the ARFM Controller. A failure could be caused by an error in installation or configuration. |
Action | Contact IBM Support. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | This reports a condition that should not happen; autonomic request flow management will ignore the server for the named cluster on the named node. |
Action | Report to IBM. |
Explanation | The ARFM Controller did not receive a CPU utilization reading for the named node within the named amount of time; that data is normally delivered by Async PMI. |
Action | Debug Async PMI config and operation. |
Explanation | Internal error. |
Action | None (this error should be reported twice, hopefully the other report will be more helpful). |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | Internal failure. Node and server level ARFM statistics will be unavailable. Charting, ARFM, and Placement functionality will be significantly degraded. |
Action | Report to IBM. |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | The background load did not behave as expected, and thus the performance management will be impaired. |
Action | Limit the background load to the configured value, or change the configured value. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | This is a consequence of an earlier failure, probably one in the range ARFM0163--0166. |
Action | Resolve the original problem. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | There cell custom property named "external.placement" has a particular syntax, and the current value violates that syntax; while the value is malformed, ARFM ignores it. |
Action | Delete the property or fix its value. |
Explanation | Internal error. |
Action | Report to IBM. |
Explanation | The performance result for the named service policy has missed the target by at least the configured amount for at least the configured time. |
Action | Diagnose and repair. |
Explanation | This is an internal failure that should not happen. |
Action | Report to IBM. |
Explanation | The values reported by the workload management component were exceptionally large, and were reduced to avoid integer overflows in subsequent calculations; this will distort those calculations unless the corresponding statistics from all the other active ODRs were reduced by the same factor. |
Action | Report to IBM. |
Explanation | This is an internal failure that should not happen. For some purposes the server will be treated like it is not an on-demand router. |
Action | Report to IBM. |
Explanation | This is a configuration error; the only supported multi-cell topology is a star with on-demand routers in only the central cell. It is impossible to correctly instantiate ARFM controllers in the current configuration. |
Action | Correct the configuration. |
Explanation | exp |
Action | ua |
Explanation | Something suspicious happened; this may or may not indicate an error. |
Action | Debug it if you can, using the information provided, or contact IBM support. |
Explanation | Something unexpected happened. |
Action | Debug it if you can, using the information provided, or contact IBM support. |