Ctl_OptFailed=ARFM1103E: The ARFM Controller {0} suffered an unexpected exception while solving the optimization (which was for {1} variables): {2} Internal failure. Consult IBM. RQM_WeightForUnkQueue=ARFM1004E: The ARFM Gateway {0} received a dequeuing weight for an unknown service class ({1}). Internal error - should never happen. Report to IBM. RQM_StatsReporterDied=ARFM1006E: The statistics generating process in ARFM Gateway {0} terminated due to failure {1}. That Gateway will generate no more statistics until the ODR containing it is started; ARFM functionality will be seriously degraded until then. Restart the ODR; report to IBM if the problem persists. MDS_SendFailed=ARFM2321E: Send of an ARFM mode message failed: {1} This is an internal communication failure. Consult IBM for help. WCORE_GENLERR=ARFM4999E: Something unexpected happened in ARFM; data is {0}, and the exception (if any) is {1}. Something unexpected happened. Debug it if you can, using the information provided, or contact IBM support. WtRO_RejectUnkMsg=ARFM2622W: {0}, in cell + Node Group {1}, received unexpected type of JMS message: {2} Internal inconsistency. Report to IBM. Ctl_OptFailed2=ARFM1105E: Allocation {0} was {1} This message provides additional detail on the preceding ARFM1103E message. No additional action required. WRSI_SendFailed=ARFM2801E: JMS-based send of an ARFM results message for cell + Node Group {0} failed: {1} This is an internal communication failure. ARFM function will be significantly degraded. Consult IBM for help. WtSO_SetArgsLengths=ARFM2662E: The ARFM weights message sender was given inconsistent args: w.length={0}, classNames.size={1} This is an internal inconsistency that should not arise. Report to IBM. Ctl_OptFailed1=ARFM1104E: Model {0} was {1} This message provides additional detail on the preceding ARFM1103E message. No additional action required. RQM_CfgIoExn=ARFM1002E: IO problem reading ARFM Gateway config file {0}: {1} This message should be gone by GA. Put a config file in the right place. AlS_SendFailed=ARFM2721E: Send of an ARFM work estimates message failed: {0} This is an internal communication failure. Consult IBM for help. Ctl_NoRhos=ARFM1109W: The ARFM Controller for {0} suffered an unexpected internal failure (to produce CPU utilizations per cluster). This should not happen. It will degrade the behavior of the Placement Controller. Report to IBM. NSS_SendFailed=ARFM2401E: Send of an ARFM NodeQStats message failed: {0} This is an internal communication failure. Consult IBM for help. Ctl_BadCapMsgA=ARFM1101E: The ARFM Controller {0} received a malformed capacity setting {1}. This is an internal inconsistency that should never arise. Internal error. Report to IBM. WtSO_SendFailed=ARFM2664E: JMS-based send of an ARFM weights message in cell + NodeGroup {0} to ARFM gateway {1} failed: {2} This is an internal communication failure. ARFM functionality will be significantly degraded. Consult IBM for help. MDSO_SendFailed=ARFM2342E: Send of an ARFM mode message failed: {0} This is an internal communication failure. Consult IBM for help. AlSO_StartupDied=ARFM2741E: A JMS-based ARFM work factor estimates message sender failed to initialize: {0} This is an internal communication failure. Check JMS provider setup for ARFM. Ctl_Initted=ARFM1107I: The ARFM Controller for {0} has been activated on this machine; control cycle length is {1} milliseconds. 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). None. TC_EmergencyUnthrottleToNormal=ARFM2844I: {0} EMERGENCY_UNTHROTTLE to NORMAL transition This internal transition is in response to an emergency condition ending. None. Ctl_NoEntryAlpha=ARFM1115W: The Work Profiler supplied no work factor for service class {2} and the entry tier {1} in cell {0}; using 1. This is a bug. Report to IBM. RQM_UnkLocalHost=ARFM1001E: java.net.InetAddress.getLocalHost().getHostName() threw UnknownHostException: {0} Code is unable to determine a hostname for the machine. Make sure the machine has an IP address. AlSq_RejectAckUnk=ARFM1981W: {0} ignoring allocation ack from unknown server {1}. Internal inconsistency. Should not happen. Consult IBM. ApRO_HandleFailed=ARFM2701E: {0} suffered unexpected exception handling received message: {1} Internal error. None; contact IBM. NSRO_HandleFailed=ARFM2381E: {0} suffered unexpected exception handling received message: {1} Internal error. None; contact IBM. AlSO_SendFailed=ARFM2742E: JMS-based send of an ARFM work factor estimates message failed: {0} This is an internal communication failure. Consult IBM for help. SSS_SendFailed=ARFM2881E: Send of an ARFM ServerStats message failed: {0} This is an internal communication failure. Consult IBM for help. DPSe_OldQStats=ARFM1241W: Speed request smoother for gateway {0} rejected QStats ending {1} because that is older than the smoother''s previous QStats (which ended at {2}). Internal error, should not happen. Report to IBM. WtSO_StartupDied=ARFM2661E: The JMS-based ARFM weights message sender for cell + nodegroup {0} failed to initialize: {1} This is an internal communication failure. Check JMS provider setup for ARFM. Ctl_NoKappaForRollup=ARFM1116W: The Work Profiler supplied no speed factor for the requests of service class {1} coming through gateway {0} to deployment target {2}. This is a bug. Report to IBM. TC_NormalToEmergencyThrottle=ARFM2841I: {0} NORMAL to EMERGENCY_THROTTLE transition This internal transition is in response to detecting an emergency condition. None. Ctl_CBNotImplemented=ARFM1113W: The ARFM Controller was configured to use the obsolete functionality known as the Concurrency Bounder --- ignored. This is an error in configuration that is not exposed to customers. Report to IBM. Ctl_NoEntryKappa=ARFM1114W: The Work Profiler supplied no speed factor for service class {2} and the entry tier {1} in cell {0}; using 1. This is a bug. Report to IBM. NSSO_StartupDied=ARFM2421E: A JMS-based ARFM NodeQStats message sender failed to initialize: {0} This is an internal communication failure. Check JMS provider setup for ARFM. TC_AsyncPmiHighUtilSensorUnfired=ARFM2850I: {0} High CPU utilization sensor unfired for node {1}. Extremely high node CPU utilization is no longer detected. None. DPWU_NoSpeedFactors=ARFM1262W: ARFM is unable to estimate the computational demands of the requests that arrive through gateway {0} due to missing speed factors. This is an internal problem that should not occur. Report to IBM. WtRO_RejectUnkObj=ARFM2621W: {0}, in cell + Node Group {1}, received unexpected type of object: {2} Internal inconsistency. Report to IBM. ESSI_SendFailed=ARFM2241E: BB-based send of an ARFM EvaldStats message for cell + Node Group {0} failed: {1} This is an internal communication failure. ARFM function will be significantly degraded. Consult IBM for help. TC_AsyncPmiDelaySensorFired=ARFM2846E: {0} Async PMI emergency sensor fired for node {1}. Async PMI messages are not being received by the ODR. None. RQM_GwUp=ARFM1009I: The ARFM Gateway for protocol family {0} and target {1} has been initialized. This is a startup status report. No action required. AlRO_HandleFailed=ARFM2061E: AllocReceiver {0} for cell {1} suffered unexpected exception handling received message: {2} Internal error. None; contact IBM. ESSO_StartupDied=ARFM2261E: The JMS-based ARFM EvaldStats message sender for cell + Node Group {0} failed to initialize: {1} This is an internal communication failure. ARFM function will be significantly degraded. Check JMS provider setup for ARFM. RQM_LogStatsCreateFailed=ARFM1005E: An ARFM Gateway failed to create a statistics log file named {0}: {1} There was some problem with the file IO; statistics will not be written to a log file. Check file name and file system state. WRSO_SendFailed=ARFM2822E: JMS-based send of an ARFM results message in cell + NodeGroup {0} to ARFM gateway {1} failed: {2} This is an internal communication failure. ARFM functionality will be significantly degraded. Consult IBM for help. StSO_StartupDied=ARFM2581E: The JMS-based ARFM QStats message sender for cell + NodeGroup {0}, ODR {1}, failed to initialize: {2} This is an internal communication failure. Check JMS provider setup for ARFM. Ctl_NoCap=ARFM1111W: The ARFM Controller skipped an optimization cycle due to complete lack of capacity information. Some other problem prevented the Controller from extracting the needed capacity information from the ODC tree. Find and fix the other problem. DPWU_NoWorkFactors=ARFM1261W: ARFM is unable to estimate the computational demands of the requests that arrive through gateway {0} due to missing work factors. This is an internal problem that should not occur. Report to IBM. Que_FollowAmongInitrs=ARFM2902E: The {0} service policy of the {1} cell applies to traffic that is subject to admission control for CPU overload protection and includes both follow-up and non-follow-up messages; an example of the latter was seen as recently as {2} and a current example of the former is {3}. 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. Revise the classification rules for the traffic currently classified into the named service policy. Ctl_BadRho=ARFM1110W: The ARFM Controller for {0} suffered an unexpected internal failure: the CPU utilization fraction for cluster {1} was found to be {2}. This should not happen. It will degrade the behavior of the Placement Controller. Report to IBM. Ctl_ManyClasses=ARFM1118E: Too many service policies ({2}) from ARFM gateway {1} in cell {0} The ARFM Controller can not handle more than 32,767 service policies, but received statistics for more than that many. If your installation really has more than 32,767 service policies, tell IBM that this limit needs to be raised, otherwise report a bug. DPSe_WrongQStats=ARFM1242W: The speed request smoother for ARFM gateway {0} saw a gap in the series of statistics messages: one message reported on a period of time ending at {2} and the next message reported on a period of time beginning at {1}. 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. Look for related problems, and report to IBM if you can not find any. MgP_ClientFailed=ARFM1082E: JMS MessagePuller {0} caught exception from client: {1} This is an unexpected internal failure. Consult IBM. TC_EmergencyThrottleToEmergencyUnthrottle=ARFM2843I: {0} EMERGENCY_THROTTLE to EMERGENCY_UNTHROTTLE transition This internal transition is in response to an emergency condition ending. None. WtRO_HandleFailed=ARFM2623E: {0}, in cell + Node Group {1}, suffered unexpected exception handling received message: {2} Internal error. None; contact IBM. TC_AsyncPmiDelaySensorUnfired=ARFM2849I: {0} Async PMI emergency sensor unfired for node {1}. Async PMI messages resumed arrival at the ODR. None. TC_ArfmSensorUnfired=ARFM2848I: {0} ARFM emergency sensor unfired. ARFM control messages resumed arrival at the ODR. None. TC_EmergencyUnthrottleToEmergencyThrottle=ARFM2842I: {0} EMERGENCY_UNTHROTTLE to EMERGENCY_THROTTLE transition This internal transition is in response to detecting an emergency condition. None. TC_AsyncPmiHighUtilSensorFired=ARFM2847E: {0} High CPU utilization sensor fired for node {1}. Extremely high node CPU utilization detected. None. Ctl_QsDrp=ARFM1119I: From {0} to {1} the autonomic request flow management gateway for the {2} protocol family in the {5} server on the {4} node in the {3} cell for messages destined for the {7} cluster in the {6} cell and having service policy {8} refused admission to {9} messages; {10} follow-up messages were not admitted; {11} of the first received transmissions of non-follow-up messages were not enqueued: {12} due to the limit on queue length, {13} due to the limit on the total number of active messages, {14} due to the logical dialog admission rate limit, {15} due to memory overload protection, and {16} due to other routing-related reasons; {17} retransmitted non-follow-up messages were also not enqueued; {18} messages were refused after spending some time in a queue. This message gives information when messages are refused admission. None required. AlSq_RejectAllocUnk=ARFM1982W: {0} ignoring allocation for unknown server {1}. Internal inconsistency. Should not happen. Consult IBM. FMM_ReadCfgFailed=ARFM1201E: Attempt to read config from file {0} failed: {1} Internal error; default configuration will be used. Check for filesystem problems; consult IBM. MgP_RcvFailed=ARFM1083E: JMS MessagePuller {0} caught exception while receiving a message: {1} This is an unexpected internal failure. Consult IBM. AlSq_OtherDealloc=ARFM1983W: {0} noted deallocation from some other source (numInst={1}, desAlloc[i]={2}). Internal inconsistency. Should not happen. Consult IBM. Ctl_NoAlphaForRollup=ARFM1117W: The Work Profiler supplied no work factor for the requests of service class {1} coming through gateway {0} to deployment target {2}. This is a bug. Report to IBM. GWD_MultiDT=ARFM1221E: ARFM Controller for {0} got data from gateway {1} that mentions more than one deployment target; {2} and {3} are two of them. Internal error; each gateway is supposed to serve only one deployment target. Report to IBM. StSO_SendFailed=ARFM2582E: JMS-based send of an ARFM QStats message for cell + NodeGroup {0}, ODR {1}, failed: {2} This is an internal communication failure. Consult IBM for help. MDSO_StartupDied=ARFM2341E: A JMS-based ARFM mode message sender failed to initialize: {0} This is an internal communication failure. Check JMS provider setup for ARFM. NSSO_SendFailed=ARFM2422E: JMS-based send of an ARFM NodeQStats message failed: {0} This is an internal communication failure. Consult IBM for help. WRSO_StartupDied=ARFM2821E: The JMS-based ARFM results message sender for cell + nodegroup {0} failed to initialize: {1} This is an internal communication failure. Check JMS provider setup for ARFM. RQM_BadGoalKind=ARFM1008E: RQM given unexpected goal kind {0} from ClassLoader {1}. Internal error - should never happen. Report to IBM. ESSO_SendFailed=ARFM2262E: JMS-based send of an ARFM EvaldStats message for cell + Node Group {0} failed: {1} This is an internal communication failure. ARFM function will be significantly degraded. Consult IBM for help. MgP_StartupDied=ARFM1081E: JMS MessagePuller {0} died at startup due to exception {1} The named ARFM component will not receive any internal messages; ARFM functionality will be severely degraded. Internal failure, consult IBM. Ctl_CreateLogFailed=ARFM1106E: ARFM Controller {0} tried to create statistics log file named {1} but failed: {2} Controller statistics will not be written to a file. Check for filesystem problems; consult IBM. WCORE_GENLWRN=ARFM4998W: Something suspicious happened in ARFM; data is {0}, and the exception (if any) is {1}. Something suspicious happened; this may or may not indicate an error. Debug it if you can, using the information provided, or contact IBM support. Ctl_CANotImplemented=ARFM1112W: The ARFM Controller was configured to use the obsolete functionality known as the Concurrency Adjuster --- ignored. This is an error in configuration that is not exposed to customers. Report to IBM. TC_ArfmSensorFired=ARFM2845E: {0} ARFM emergency sensor fired. ARFM control messages are not being received by the ODR. None. Que_InitrAmongFollows=ARFM2901E: The {0} service policy of the {1} cell applies to traffic that is subject to admission control for CPU overload protection and includes both follow-up and non-follow-up messages; an example of the former was seen as recently as {2} and a current example of the latter is {3}. 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. Revise the classification rules for the traffic currently classified into the named service policy. RQM_NqsWrongCell=ARFM1007E: The ARFM Gateway with ID {1} in cell {0} was asked to produce NodeQStats for node {3} in cell {2}. Internal error - should never happen. Report to IBM. RQM_CfgParseExn=ARFM1003E: Problem parsing ARFM Gateway config file {0}: {1} This message should be gone by GA. Fix format error in config file. Ctl_Stopped=ARFM1108I: The ARFM Controller for {0} has been shutdown on this machine. 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). None. Ctl_DidntUseAll=ARFM1102W: The ARFM Controller {0} chose to use only {1} seats when {2} were available. This usually indicates something is broken. Consult IBM. WtSO_SendJmsFailed=ARFM2663E: JMS-based send of an ARFM weights message in cell + NodeGroup {0} to ARFM gateway {1} suffered a JMS failure: {2} This is an internal communication failure. ARFM functionality will be significantly degraded. Check JMS configuration for ARFM. Consult IBM for help.