Explanation | Code is unable to determine a hostname for the machine. |
Action | Make sure the machine has an IP address. |
Explanation | This message should be gone by GA. |
Action | Put a config file in the right place. |
Explanation | This message should be gone by GA. |
Action | Fix format error in config file. |
Explanation | Internal error - should never happen. |
Action | Report to IBM. |
Explanation | There was some problem with the file IO; statistics will not be written to a log file. |
Action | Check file name and file system state. |
Explanation | That Gateway will generate no more statistics until the ODR containing it is started; ARFM functionality will be seriously degraded until then. |
Action | Restart the ODR; report to IBM if the problem persists. |
Explanation | Internal error - should never happen. |
Action | Report to IBM. |
Explanation | Internal error - should never happen. |
Action | Report to IBM. |
Explanation | This is a startup status report. |
Action | No action required. |
Explanation | The named ARFM component will not receive any internal messages; ARFM functionality will be severely degraded. |
Action | Internal failure, consult IBM. |
Explanation | This is an unexpected internal failure. |
Action | Consult IBM. |
Explanation | This is an unexpected internal failure. |
Action | Consult IBM. |
Explanation | This is an internal inconsistency that should never arise. |
Action | Internal error. Report to IBM. |
Explanation | This usually indicates something is broken. |
Action | Consult IBM. |
Explanation | Internal failure. |
Action | Consult IBM. |
Explanation | This message provides additional detail on the preceding ARFM1103E message. |
Action | No additional action required. |
Explanation | This message provides additional detail on the preceding ARFM1103E message. |
Action | No additional action required. |
Explanation | Controller statistics will not be written to a file. |
Action | Check for filesystem problems; consult IBM. |
Explanation | The local instance of the Autonomic Request Flow Management controllers MBean for the named cell has been activated (a cell has an ARFM Controllers MBean instance in each ODR, node agent, and deployment manager, for high availability; only one is activated at a time). |
Action | None. |
Explanation | The local instance of the Autonomic Request Flow Management controllers MBean for the named cell has been deactivated (a cell has an ARFM Controllers MBean instance in each ODR, node agent, and deployment manager, for high availability; only one is activated at a time). |
Action | None. |
Explanation | This should not happen. It will degrade the behavior of the Placement Controller. |
Action | Report to IBM. |
Explanation | This should not happen. It will degrade the behavior of the Placement Controller. |
Action | Report to IBM. |
Explanation | Some other problem prevented the Controller from extracting the needed capacity information from the ODC tree. |
Action | Find and fix the other problem. |
Explanation | This is an error in configuration that is not exposed to customers. |
Action | Report to IBM. |
Explanation | This is an error in configuration that is not exposed to customers. |
Action | Report to IBM. |
Explanation | This is a bug. |
Action | Report to IBM. |
Explanation | This is a bug. |
Action | Report to IBM. |
Explanation | This is a bug. |
Action | Report to IBM. |
Explanation | This is a bug. |
Action | Report to IBM. |
Explanation | The ARFM Controller can not handle more than 32,767 service policies, but received statistics for more than that many. |
Action | If your installation really has more than 32,767 service policies, tell IBM that this limit needs to be raised, otherwise report a bug. |
Explanation | This message gives information when messages are refused admission. |
Action | None required. |
Explanation | Internal error; default configuration will be used. |
Action | Check for filesystem problems; consult IBM. |
Explanation | Internal error; each gateway is supposed to serve only one deployment target. |
Action | Report to IBM. |
Explanation | Internal error, should not happen. |
Action | Report to IBM. |
Explanation | This is an internal problem that should not normally occur; sometimes it occurs as a consequence of other problems that disrupt the operation of the ARFM controller. |
Action | Look for related problems, and report to IBM if you can not find any. |
Explanation | This is an internal problem that should not occur. |
Action | Report to IBM. |
Explanation | This is an internal problem that should not occur. |
Action | Report to IBM. |
Explanation | Internal inconsistency. Should not happen. |
Action | Consult IBM. |
Explanation | Internal inconsistency. Should not happen. |
Action | Consult IBM. |
Explanation | Internal inconsistency. Should not happen. |
Action | Consult IBM. |
Explanation | Internal error. |
Action | None; contact IBM. |
Explanation | This is an internal communication failure. ARFM function will be significantly degraded. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. ARFM function will be significantly degraded. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal communication failure. ARFM function will be significantly degraded. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | Internal error. |
Action | None; contact IBM. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | Internal inconsistency. |
Action | Report to IBM. |
Explanation | Internal inconsistency. |
Action | Report to IBM. |
Explanation | Internal error. |
Action | None; contact IBM. |
Explanation | This is an internal communication failure. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal inconsistency that should not arise. |
Action | Report to IBM. |
Explanation | This is an internal communication failure. ARFM functionality will be significantly degraded. |
Action | Check JMS configuration for ARFM. Consult IBM for help. |
Explanation | This is an internal communication failure. ARFM functionality will be significantly degraded. |
Action | Consult IBM for help. |
Explanation | Internal error. |
Action | None; contact IBM. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. ARFM function will be significantly degraded. |
Action | Consult IBM for help. |
Explanation | This is an internal communication failure. |
Action | Check JMS provider setup for ARFM. |
Explanation | This is an internal communication failure. ARFM functionality will be significantly degraded. |
Action | Consult IBM for help. |
Explanation | This internal transition is in response to detecting an emergency condition. |
Action | None. |
Explanation | This internal transition is in response to detecting an emergency condition. |
Action | None. |
Explanation | This internal transition is in response to an emergency condition ending. |
Action | None. |
Explanation | This internal transition is in response to an emergency condition ending. |
Action | None. |
Explanation | ARFM control messages are not being received by the ODR. |
Action | None. |
Explanation | Async PMI messages are not being received by the ODR. |
Action | None. |
Explanation | Extremely high node CPU utilization detected. |
Action | None. |
Explanation | ARFM control messages resumed arrival at the ODR. |
Action | None. |
Explanation | Async PMI messages resumed arrival at the ODR. |
Action | None. |
Explanation | Extremely high node CPU utilization is no longer detected. |
Action | None. |
Explanation | This is an internal communication failure. |
Action | Consult IBM for help. |
Explanation | A service policy that applies to traffic subject to admission control for CPU overload protection should apply exclusively to follow-up messages or exclusively to non-follow-up messages; a follow-up message is one that is part of a pre-existing session or dialog. |
Action | Revise the classification rules for the traffic currently classified into the named service policy. |
Explanation | A service policy that applies to traffic subject to admission control for CPU overload protection should apply exclusively to follow-up messages or exclusively to non-follow-up messages; a follow-up message is one that is part of a pre-existing session or dialog. |
Action | Revise the classification rules for the traffic currently classified into the named service policy. |
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. |