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}.
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}.


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.proxy.nls.Messages.dita
File name: com.ibm.wsmm.proxy.nls.Messages.html