WXDH

WXDH0002I: Starting the health controller for {0}.
WXDH0003I: Stopping the health controller for {0}.
WXDH0004I: The health controller is already started.
WXDH0005E: An exception occurred while enabling the health controller: {0}
WXDH0006E: Health policy not found: {0}
WXDH0007W: Member {0} is not found for health policy {1}.
WXDH0008E: An error occurred during the initialization of the health controller: {0}
WXDH0009E: An error occurred while stopping the health controller: {0}
WXDH0010W: Unexpected restart state {0} for server {1}.
WXDH0011W: Server {0} exceeded the maximum amount of verification failures: Disabling restarts.
WXDH0012W: Server {0} with restarts disabled failed the health check.
WXDH0014E: Cannot find the node group for node {0}, {1}.
WXDH0015E: Cannot find target member {0} for health policy {1}.
WXDH0016W: An error occurred while reading the configuration repository {0}.
WXDH0017E: The HealthConfigMonitor could not be located on the deployment manager.
WXDH0019E: The server configuration listener could not be started.
WXDH0021E: The following error occurred during the start of the configuration listener: {0}
WXDH0022E: The following error occurred while handling configuration notification: {0}
WXDH0028E: The following exception occurred while disabling the controller: {0}
WXDH0029I: Server {0} cannot be restarted, because the restart process is prohibited at this time.
WXDH0030W: Server {0} cannot be restarted.
WXDH0031I: Server {0} cannot be restarted when the node is in maintenance mode.
WXDH0032I: Server {0} cannot be restarted, because the last attempt to restart the server occurred too recently.
WXDH0033W: Server {0} cannot be restarted, because it is the only running member of a cluster.
WXDH0034I: Health policy {0} has been added.
WXDH0035E: Health policy {0} could not be added.
WXDH0036I: Health policy {0} has been removed.
WXDH0037I: The {0} for health policy {1} has changed to {2}.
WXDH0038E: The {0} of health policy {1} could not be changed.
WXDH0039I: Member {0} has been added to health policy {1}.
WXDH0040E: Member {0} could not be added to health policy {1}.
WXDH0041I: Member {0} has been removed from health policy {1}.
WXDH0042I: The {0} reaction has been added to health policy {1}.
WXDH0043I: The {0} reaction has been removed from health policy {1}.
WXDH0044W: Member {0} of health policy {1} is not adjacent to the on demand router.
WXDH0045E: The following error occurred locating the {0} bulletin board: {1}
WXDH0046E: The following error occurred starting the health controller: {0}
WXDH0048I: Server {0} cannot be restarted when performing long-running work.
WXDH0049I: Server {0} cannot be restarted when the node switches between long-running and transactional work.
WXDH0050W: The health condition of policy {0} does not apply to servers performing long-running work.
WXDH0051W: Health policy {0} is not supported for the other middleware server {1}.
WXDH1001E: The following error occurred when trying to stop server {0}: {1}
WXDH1002E: The following error occurred when trying to communicate with the node agent on {0}.
WXDH1003E: The following error occurred when trying to start server {0}.
WXDH1004E: The following error occurred when trying to locate server {0}.
WXDH1005E: Heap dumps are not supported on server {0}.
WXDH1006I: A heap dump was automatically generated on server {0} in file {1}.
WXDH1007I: Server {0} is being restarted automatically.
WXDH1008I: Server {0} was restarted successfully.
WXDH1009E: The restart operation for server {0} failed.
WXDH1010I: A thread dump for server {0} is being issued.
WXDH1011I: The health controller issued a thread dump for server {0}.
WXDH1012E: The thread dump operation failed for server {0}.
WXDH1013E: The thread dump failed for server {0}.
WXDH1014I: Heap dumps for server {0} are being issued automatically.
WXDH1015E: The heap dump failed for server {0}.
WXDH1016E: The heap dump failed for server {0}.
WXDH1017I: The following heap dumps were generated for server {0}: {1}
WXDH1018E: Could not contact the application placement controller: {0}
WXDH1019E: Server {0} cannot be restarted, the application placement controller is disabled, and the minimum number of instances cannot be maintained.
WXDH1020E: Server {0} cannot be restarted, and the minimum number of cluster instances cannot be maintained.
WXDH1021W: The plan generated for server {0} and condition {1} is no longer valid.
WXDH1022I: Starting the custom task {0} on target {1}.
WXDH1023I: Custom task {0} successfully started and completed.
WXDH1024E: The attempt to start and complete custom task {0} failed.
WXDH1025I: Maintenance mode is being set for server {0}.
WXDH1026I: Server {0} was successfully placed into maintenance mode.
WXDH1027E: An error occurred while attempting to place server {0} into maintenance mode.
WXDH1028W: The server {0} failed to stop. A force terminate command has been issued.
WXDH1029I: A SNMP trap has been issued for server {0}.
WXDH1030E: The attempt to issue a SNMP trap for server {0} failed.
WXDH1120I: The Health Controller recommends server {0} be changed to state {1} on node {2}. Policy {3} reaction mode is {4}.
WXDH1121I: The Health Controller has submitted a task to the Task Management subsystem that will expire at {0}. The operating mode is {1}. The task ID is {2}.
WXDH1122I: The Health Controller has submitted a task that was denied. The task ID is {0}.
WXDH1123I: The Health Controller has received approval for task ID {0}.
WXDH1124I: The Health Controller has submitted a task that has expired. The task ID is {0}.
WXDH1125I: The Health Controller will submit tasks from the active location {0}.
WXDH1128W: The Health Controller has asked to find an alternate location to run server {0} and a replacement location is not available.
WXDH1129I: The Health Controller has asked to find an alternate location to run server {0} and the available replacement location is {1}.
WXDH1130I: The Health Controller has asked to find an alternate location to run server {0} and a replacement location is not needed. The server can be stopped or placed into maintenance mode.
WXDH1132I: The Health Controller has issued command {0} for task ID {1} on server {2} that will expire at {3}.
WXDH1133I: The Health Controller has received status for command {0} for task ID {1} on server {2}. success={3}
WXDH1140I: The Health Controller has selected an alternate location to run server {0}. The replacement location is {1}.
WXDH1141W: The Health Controller can not locate an alternate location to run server {0}. Reason Code {1}.
WXDH1142W: The Health Controller is placing dynamic cluster {0} into {1} operating mode.
WXDH2001W: Thread hang detection is disabled or its status cannot be obtained for server {0}.
WXDH3001E: No sensor data was received during the control cycle from server {0} for health policy {1}.
WXDH3002W: The maximum server age specified by policy {0} was reached by server {1} on node {2}. The limit is {3} hours and the current age is {4} hours.
WXDH3003W: The maximum number of requests specified by policy {0} was reached by server {1} on node {2}. The limit is {3} requests and the current work is {4} requests.
WXDH3004W: The memory consumption limit specified by policy {0} was exceeded by server {1} on node {2}. The limit is {3} % and the current heap size is {4} % of the maximum of {5} KB.
WXDH3005W: The average response time limit specified by policy {0} was exceeded by server {1} on node {2}. The limit is {3} ms and the current value is {4} ms.
WXDH3006W: A storm drain condition is suspected by policy {0} for server {1} on node {2}. The average response time has dropped to {3} milliseconds.
WXDH3007W: The request timeout limit specified by policy {0} was exceeded by server {1} on node {2}. The limit is {3} % and the current timeout fraction is {4} %.
WXDH3008W: A memory leak is suspected by policy {0} for server {1} on node {2}.
WXDH3009W: A servlet response time change point has been detected by health policy {0} for server {1} on node {2}: Suspected servlets are: {3}.
WXDH3010W: A server response time change point has been detected for server {0} on node {1}. The average response time has changed from {2} ms to {3} ms.
WXDH3011W: A response time change point has been detected by health policy {0} for server {1} on node {2} for the average EJB method response time: Suspected EJBs are: {3}.
WXDH3012W: The request timeout limit specified by policy {0} was exceeded by server {1} on node {2}. The limit is {3} % and the current timeout fraction is {4} %. A total of {5} threads may be hung.
WXDH3013W: A custom health condition violation is suspected by health policy {0} for server {1} on node {2}.
WXDH3014W: The average response time limit specified by policy {0} was exceeded by server {1} on node {2}. The problem was detected by the following Intelligent Management routers: {3}
WXDH3015W: The request timeout limit specified by policy {0} was exceeded by server {1} on node {2}. The problem was detected by the following Intelligent Management routers: {3}
WXDH5000I: The health management controller is running and operational.
WXDH5001I: The complete set of states for a healthy health management controller is: {0}
WXDH5002E: The complete set of states for an unhealthy health management controller is: {0}
WXDH9999E: Health controller internal error: data is {0}, and the exception 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.ws.xd.hmm.nls.Messages.dita
File name: com.ibm.ws.xd.hmm.nls.Messages.html