ARFM

ARFM0001E: MapRequestFilter not configured (request context was {0}).
ARFM0002E: java.net.InetAddress.getLocalHost().getHostName() threw UnknownHostException: {0}
ARFM0003E: Cannot happen.
ARFM0004I: ARFM HTTP Filters initialized.
ARFM0005E: The ARFM Filter suffered unexpected exception {0} constructing a ReqQMgr to handle request {1} for deployment target {2} in cell {3}.
ARFM0006E: The ARFM Filter previously suffered some unexpected exception while constructing a ReqQMgr to handle a previous request, and will now pass without delay request {0} for deployment target {1} in cell {2}.
ARFM0007I: ARFM SIP Filters initialized.
ARFM0008I: Response code {0} will be used to reject HTTP messages due to overload.
ARFM0009I: Response code {0} will be used to reject SIP/TCP messages, and code {1} will be used to reject SIP/UDP messages, due to overload.
ARFM0021E: No ARFM ID attached to response {0}.
ARFM0022E: Null ReqQMgr attached to response {0}.
ARFM0041E: unexpected Throwable aborted compilation of classification policy; {0}
ARFM0042E: unexpected exception aborted request classification; uriNode={0}, context={1}, exn={2}
ARFM0043E: The ODC tree has no Node for Server {2}, which is the deployment target for the Web Module {1}, which handles URIs of the form {0}.
ARFM0044E: The ODC tree has no deployment target for Web Module {1}, which handles URIs of the form {0}.
ARFM0045W: ARFM is unsure whether to do overload protection and queuing for traffic destined to node {0} because its operating system ({1}) is unexpected.
ARFM0046E: The on-demand configuration tree contains a module, named {0}, that has no associated clusters.
ARFM0047E: The on-demand configuration tree contains a cluster (named {0}) that is deployed to a node group (named {1}) that contains no nodes.
ARFM0061W: Unexpected exception arose when looking up the FilterManagerService: {0}
ARFM0062I: ARFM Gateway disabled because this is not an ODR process.
ARFM0063I: ARFM filters are disabled by ARFM configuration.
ARFM0081E: Failed to get ODC Tree: {0}
ARFM0082E: Failed to find cell {0} in the ODC Tree.
ARFM0085E: ODC Tree changed while locked for read: in cell {0}, server {1} has previously unknown cluster {2}.
ARFM0096E: While reading the CPU utilizations for clusters {1} in cell {0}, the ARFM Controller suffered an unexpected exception: {2}.
ARFM0097E: Backstop stat production process for node {1} in cell {0} terminated unexpectedly due to failure {2}.
ARFM0099E: Unexpected ODCException while examining server {0} on node {1} in cell {2}: {3}
ARFM0100W: Ignoring cluster {2} on node {1} while estimating computing power of cell {0}.
ARFM0101W: Node {0} did not report CPU utilization within the last {1} seconds.
ARFM0121E: Exception aborted load balancing of request context {0}, with attributes {1}: {2}.
ARFM0122E: Resume failed for context {0}, with attributes {1}: {2}.
ARFM0123E: ARFM failed to get an ODCHelper: {2}.
ARFM0141E: Unexpected ODC Exception: {0}.
ARFM0142E: Backstop NodeQStats production will not happen because of unexpected exception: {0}.
ARFM0161E: For the interval ending {2}, node {1} in cell {0} had a background CPU load of {3} percent, which exceeds the configured limit of {4}.
ARFM0162E: Found multiple Balancer states for node {1} in cell {0}, one from {2} and another from {3}; using the first ({4}).
ARFM0163E: Unable to obtain BulletinBoardFactory at startup.
ARFM0164E: Attempt to find BulletinBoard named {0} failed: {1}.
ARFM0165E: Lookup of BulletinBoard named {0} returned null!
ARFM0166E: Lookup of remote BulletinBoardScope for cell named {0} failed: {1}.
ARFM0167E: An attempt to subscribe WebSphere Business Grid Balancer state for node {1} in cell {0} failed: {2}.
ARFM0168E: An attempt to close subscription to WebSphere Business Grid Balancer state for node {1} in cell {0} failed: {2}.
ARFM0169E: Internal inconsistency, concerning node {1} of cell {0}.
ARFM0170W: Unable to track WebSphere Business Grid Balancer state for node {1} in cell {0} due to some earlier failure.
ARFM0171E: Internal initialization failure: {0}.
ARFM0172E: Internal failure regarding server {2} on node {1} in cell {0}: {3}.
ARFM0173W: Internal failure (cell={0}, node={1}, toNotify={2}).
ARFM0201E: Did not find the ODR cell (named {0}) in the ODC tree.
ARFM0202E: Unexpected ODC Exception fetching external.nodes property from cell {0}: {1}.
ARFM0203E: Syntax error in external.placement custom property (value is "{1}") of the {0} cell: {2}.
ARFM0241E: ARFM suffered unexpected problem reading the ODC tree for cell {0}: {1}
ARFM0261E: Service policy {1} in cell {0} has suffered a serious violation since {2}.
ARFM0262E: The ARFM Controller for cell {0} suffered an unexpected exception when submitting its current list of service policy violation tasks to the task manager.
ARFM0263W: The autonomic request flow management statistics for messages admissible to server {0} on node {1} in cell {2} for the sake of memory overload protection ({3} tests, {4} passes) were reduced by a factor of {5}.
ARFM0281E: An unexpected exception arose when trying to read the On-Demand Configuration property named ODR for the server {2} on the node {1} in the cell {0}: {3}.
ARFM0282E: There are on-demand routers in two connected cells: one router is server {2} on node {1} in cell {0} and another is server {5} on node {4} in cell {3}.
ARFM0283W: MultiCell configuration detected without CenterCell custom property setting in any cell: Number of cells detected {0}.
ARFM0501E: Error with one parm, {0}
ARFM0998W: Something suspicious happened in ARFM; data is {0}, and the exception (if any) is {1}.
ARFM0999E: Something unexpected happened in ARFM; data is {0}, and the exception (if any) is {1}.
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}.
ARFM4001E: An Error occurs when setting QTI listener; data is {0}, and the exception is {1}.
ARFM4002E: ODC initialization failure: {0}.
ARFM4021E: An Error occurs when getting or setting DialogAux; data is {0}, and the exception is {1}.
ARFM4061E: An Error occurs when setting DialogAux; data is {0}, and the exception is {1}.
ARFM4081E: An unexpected runtime exception occurred while initializing the SIP statistics gatherer for autonomic request flow management: {0}.
ARFM4082I: Initialized the SIP statistics gatherer for autonomic request flow management.
ARFM4083I: The SIP statistics gatherer for autonomic request flow management is disabled.
ARFM4084I: Autonomic memory overload protection is enabled.
ARFM4085I: Autonomic memory overload protection is disabled.
ARFM4101E: ODC initialization failure: {0}.
ARFM4102W: Fail to load the JVM arguments on IBM JVM. {0}.
ARFM4103E: Importance threshold report failed. Server: {0}. Exception: {1}
ARFM4104I: Absent an override via the explicitGcPeriod cluster custom property, autonomic memory overload protection will wait {0} seconds between explicitly triggered garbage collections.
ARFM4105I: Absent an override via the explicitGcPeriod cluster custom property, autonomic memory overload protection will not explicitly trigger garbage collections.
ARFM4106I: Absent an override via the explicitGcPeriod cluster custom property, the time between explicit garbage collections for the purpose of memory overload protection will be relative to the configured time between successive settings of the memory overload protection control value in the On-Demand Configuration facility.
ARFM4107I: The maximum heap size is {0} bytes; the low threshold for memory overload protection is {1} bytes and the high threshold is {2} bytes.
ARFM4108I: Absent an override via the maxNonFullGcMemoryRelease cluster custom property, autonomic memory overload protection will figure a full garbage collection has happened when more than {0} kilobytes have been freed.
ARFM4109I: Absent an override via the maxNonFullGcMemoryRelease cluster custom property, autonomic memory overload protection will assume every garbage collection is a full one.
ARFM4110I: Absent an override via the maxNonFullGcMemoryRelease cluster custom property, autonomic memory overload protection will assume no garbage collection is a full one.
ARFM4111I: Generational garbage collection is in use in an IBM JRE, but the nursery size limit is not known exactly; assuming {0} kilobytes.
ARFM4112I: Generational garbage collection is in use in a non-IBM JRE, but the nursery size limit is not known.
ARFM4113E: The memory overload protection controller suffered an unexpected error when looking up the local process in the On-Demand Configuration facility: {0}
ARFM4114I: The memory overload protection controller explicitly invoked a garbage collection (GC) at {0}; the previous detected major GC was at {1}, and the configured minimum time between explicit GCs was {2} seconds; the last time a heap usage sample was below {3} was {4}; the number of HTTP admissibility tests was {5} and {6} passed, and the choke fraction is {7}; the number of SIP admissibility tests was {8} and {9} passed, and the choke fraction is {10}; it is {11} that the garbage collector values throughput over pause times.
ARFM4115I: The memory overload protection controller explicitly invoked a garbage collection (GC) at {0}; the previous detected major GC was at {1}, at which time the heap utilization became {2} percent, which is above the threshold of {3} percent; the configured minimum time between explicit GCs was {4} seconds; the number of HTTP admissibility tests was {5} and {6} passed, and the choke fraction is {7}; the number of SIP admissibility tests was {8} and {9} passed, and the choke fraction is {10}; it is {11} that the garbage collector values throughput over pause times.
ARFM4898W: Something suspicious happened in ARFM; data is {0}, and the exception (if any) is {1}.
ARFM4899E: Something unexpected happened in ARFM; data is {0}, and the exception (if any) is {1}.
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}.
ARFM5001E: ARFM suffered unexpected exception parsing internal config from properties file {0}: {1}.
ARFM5002E: Failed to get ODC Tree: {0}
ARFM5004E: ARFM found no ODC vertex for the cell named {0}.
ARFM5006E: ARFM for cell {0} suffered unexpected exception parsing config (some from ODC, some from file {1}): {2}.
ARFM5007I: ARFM configuration for cell {0} is {1}.
ARFM5021E: ARFM suffered unexpected failure during ODC setup: {0}
ARFM5022E: ARFM suffered unexpected failure while looking up and reading configuration from ODC vertex for cell {0}: {1}.
ARFM5023E: ARFM got unexpected ODC event type.
ARFM5024E: ARFM suffered unexpected exception while handling ODC event: {0}.
ARFM5041E: ARFM suffered unexpected failure while looking up and reading configuration from ODC vertex for the cell {0}: {1}.
ARFM5998W: Something suspicious happened in ARFM; data is {0}, and the exception (if any) is {1}.
ARFM5999E: Something unexpected happened in ARFM; data is {0}, and the exception (if any) is {1}.
ARFM6001E: Got I/O exception {2} while reading WSMM configuration from {1} for {0}; using defaults.
ARFM6002E: {0} is broken by exception while parsing config info from {1}: {2}.
ARFM8001E: ARFM Controller configuration file {0} cannot be read.
ARFM8002E: Cannot happen.
ARFM8003W: Unexpected exception arose when looking up the FilterManagerService: {0}
ARFM8004I: ARFM Controller disabled because this is not an ODR process.
ARFM8005I: ARFM Controller disabled because it is configured to run in the HTTP Proxy Filter.
ARFM8021E: Failed to get ODC Tree: {0}
ARFM8022E: Failed to read ODC Tree: {0}
ARFM8023I: Starting ARFM controller for cell {0}, due to activation by HA-Manager.
ARFM8024I: Stopping ARFM controller for cell {0}, due to de-activation by HA-Manager.
ARFM8025W: Unknown edge change event {0}.
ARFM8026W: Unknown topology change event {0}.
ARFM8027E: Attempt to instantiate ARFM Controller for node group {0} in cell {1} suffered unexpected failure: {2}.
ARFM8028I: Starting ARFM controller for cell {0}, due to On-Demand Configuration (ODC) change.
ARFM8029I: Stopping ARFM controller for cell {0}, due to On-Demand Configuration (ODC) change.
ARFM8030E: Unexpected exception arose while enabling or disabling ARFM controllers in the {0} cell (note: the central cell is {1} and the other connected cells are {2}): {3}.
ARFM8031I: Starting ARFM controller for cell {0}, to implement a reset.
ARFM8032I: Stopping ARFM controller for cell {0}, to implement a reset.
ARFM8101E: The ARFM for cell {0} suffered an unexpected exception/error when trying to find the location of the MBean holding its controllers; the exception/error is {1}.
ARFM8102E: The component status provider for ARFM suffered an unexpected exception when trying to query the ARFM controllers MBean: {0}.
ARFM8501E: Error with one parm, {0}
ARFM8998W: Something suspicious happened in ARFM; data is {0}, and the exception (if any) is {1}.
ARFM8999E: Something unexpected happened in ARFM; data is {0}, and the exception (if any) is {1}.