ARFM

ARFM1001E: java.net.InetAddress.getLocalHost().getHostName() threw UnknownHostException: {0}
ARFM1002E: IO problem reading ARFM Gateway config file {0}: {1}
ARFM1003E: Problem parsing ARFM Gateway config file {0}: {1}
ARFM1004E: The ARFM Gateway {0} received a dequeuing weight for an unknown service class ({1}).
ARFM1005E: An ARFM Gateway failed to create a statistics log file named {0}: {1}
ARFM1006E: The statistics generating process in ARFM Gateway {0} terminated due to failure {1}.
ARFM1007E: The ARFM Gateway with ID {1} in cell {0} was asked to produce NodeQStats for node {3} in cell {2}.
ARFM1008E: RQM given unexpected goal kind {0} from ClassLoader {1}.
ARFM1009I: The ARFM Gateway for protocol family {0} and target {1} has been initialized.
ARFM1081E: JMS MessagePuller {0} died at startup due to exception {1}
ARFM1082E: JMS MessagePuller {0} caught exception from client: {1}
ARFM1083E: JMS MessagePuller {0} caught exception while receiving a message: {1}
ARFM1101E: The ARFM Controller {0} received a malformed capacity setting {1}.
ARFM1102W: The ARFM Controller {0} chose to use only {1} seats when {2} were available.
ARFM1103E: The ARFM Controller {0} suffered an unexpected exception while solving the optimization (which was for {1} variables): {2}
ARFM1104E: Model {0} was {1}
ARFM1105E: Allocation {0} was {1}
ARFM1106E: ARFM Controller {0} tried to create statistics log file named {1} but failed: {2}
ARFM1107I: The ARFM Controller for {0} has been activated on this machine; control cycle length is {1} milliseconds.
ARFM1108I: The ARFM Controller for {0} has been shutdown on this machine.
ARFM1109W: The ARFM Controller for {0} suffered an unexpected internal failure (to produce CPU utilizations per cluster).
ARFM1110W: The ARFM Controller for {0} suffered an unexpected internal failure: the CPU utilization fraction for cluster {1} was found to be {2}.
ARFM1111W: The ARFM Controller skipped an optimization cycle due to complete lack of capacity information.
ARFM1112W: The ARFM Controller was configured to use the obsolete functionality known as the Concurrency Adjuster --- ignored.
ARFM1113W: The ARFM Controller was configured to use the obsolete functionality known as the Concurrency Bounder --- ignored.
ARFM1114W: The Work Profiler supplied no speed factor for service class {2} and the entry tier {1} in cell {0}; using 1.
ARFM1115W: The Work Profiler supplied no work factor for service class {2} and the entry tier {1} in cell {0}; using 1.
ARFM1116W: The Work Profiler supplied no speed factor for the requests of service class {1} coming through gateway {0} to deployment target {2}.
ARFM1117W: The Work Profiler supplied no work factor for the requests of service class {1} coming through gateway {0} to deployment target {2}.
ARFM1118E: Too many service policies ({2}) from ARFM gateway {1} in cell {0}
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.
ARFM1201E: Attempt to read config from file {0} failed: {1}
ARFM1221E: ARFM Controller for {0} got data from gateway {1} that mentions more than one deployment target; {2} and {3} are two of them.
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}).
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}.
ARFM1261W: ARFM is unable to estimate the computational demands of the requests that arrive through gateway {0} due to missing work factors.
ARFM1262W: ARFM is unable to estimate the computational demands of the requests that arrive through gateway {0} due to missing speed factors.
ARFM1981W: {0} ignoring allocation ack from unknown server {1}.
ARFM1982W: {0} ignoring allocation for unknown server {1}.
ARFM1983W: {0} noted deallocation from some other source (numInst={1}, desAlloc[i]={2}).
ARFM2061E: AllocReceiver {0} for cell {1} suffered unexpected exception handling received message: {2}
ARFM2241E: BB-based send of an ARFM EvaldStats message for cell + Node Group {0} failed: {1}
ARFM2261E: The JMS-based ARFM EvaldStats message sender for cell + Node Group {0} failed to initialize: {1}
ARFM2262E: JMS-based send of an ARFM EvaldStats message for cell + Node Group {0} failed: {1}
ARFM2321E: Send of an ARFM mode message failed: {1}
ARFM2341E: A JMS-based ARFM mode message sender failed to initialize: {0}
ARFM2342E: Send of an ARFM mode message failed: {0}
ARFM2381E: {0} suffered unexpected exception handling received message: {1}
ARFM2401E: Send of an ARFM NodeQStats message failed: {0}
ARFM2421E: A JMS-based ARFM NodeQStats message sender failed to initialize: {0}
ARFM2422E: JMS-based send of an ARFM NodeQStats message failed: {0}
ARFM2581E: The JMS-based ARFM QStats message sender for cell + NodeGroup {0}, ODR {1}, failed to initialize: {2}
ARFM2582E: JMS-based send of an ARFM QStats message for cell + NodeGroup {0}, ODR {1}, failed: {2}
ARFM2621W: {0}, in cell + Node Group {1}, received unexpected type of object: {2}
ARFM2622W: {0}, in cell + Node Group {1}, received unexpected type of JMS message: {2}
ARFM2623E: {0}, in cell + Node Group {1}, suffered unexpected exception handling received message: {2}
ARFM2661E: The JMS-based ARFM weights message sender for cell + nodegroup {0} failed to initialize: {1}
ARFM2662E: The ARFM weights message sender was given inconsistent args: w.length={0}, classNames.size={1}
ARFM2663E: JMS-based send of an ARFM weights message in cell + NodeGroup {0} to ARFM gateway {1} suffered a JMS failure: {2}
ARFM2664E: JMS-based send of an ARFM weights message in cell + NodeGroup {0} to ARFM gateway {1} failed: {2}
ARFM2701E: {0} suffered unexpected exception handling received message: {1}
ARFM2721E: Send of an ARFM work estimates message failed: {0}
ARFM2741E: A JMS-based ARFM work factor estimates message sender failed to initialize: {0}
ARFM2742E: JMS-based send of an ARFM work factor estimates message failed: {0}
ARFM2801E: JMS-based send of an ARFM results message for cell + Node Group {0} failed: {1}
ARFM2821E: The JMS-based ARFM results message sender for cell + nodegroup {0} failed to initialize: {1}
ARFM2822E: JMS-based send of an ARFM results message in cell + NodeGroup {0} to ARFM gateway {1} failed: {2}
ARFM2841I: {0} NORMAL to EMERGENCY_THROTTLE transition
ARFM2842I: {0} EMERGENCY_UNTHROTTLE to EMERGENCY_THROTTLE transition
ARFM2843I: {0} EMERGENCY_THROTTLE to EMERGENCY_UNTHROTTLE transition
ARFM2844I: {0} EMERGENCY_UNTHROTTLE to NORMAL transition
ARFM2845E: {0} ARFM emergency sensor fired.
ARFM2846E: {0} Async PMI emergency sensor fired for node {1}.
ARFM2847E: {0} High CPU utilization sensor fired for node {1}.
ARFM2848I: {0} ARFM emergency sensor unfired.
ARFM2849I: {0} Async PMI emergency sensor unfired for node {1}.
ARFM2850I: {0} High CPU utilization sensor unfired for node {1}.
ARFM2881E: Send of an ARFM ServerStats message failed: {0}
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}.
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}.
ARFM4998W: Something suspicious happened in ARFM; data is {0}, and the exception (if any) is {1}.
ARFM4999E: Something unexpected happened in ARFM; data is {0}, and the exception (if any) is {1}.


Terms and conditions for information centers | Feedback

Last updated: June 12, 2013 12:15 PM EDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.wsmm.nls.Messages.dita
File name: com.ibm.wsmm.nls.Messages.html