Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An exception occurred as the health controller was being enabled. |
Action | Contact IBM Support. |
Explanation | The specified health policy was not found. |
Action | Verify that the cell is fully synchronized and is displayed on the Health Policies panel. In the administrative console, select Operational policies > Health Policies. |
Explanation | The health policy member could not be found or removed. |
Action | Verify that the cell is fully synchronized and is displayed in the health policy. In the administrative console, select Operational policies > Health Policies > health_policy_name > Memberships. |
Explanation | An error occurred during the initialization of the health controller. |
Action | Contact IBM Support. |
Explanation | An error occurred while stopping the health controller. |
Action | Contact IBM Support. |
Explanation | The health controller encountered an unexpected state. |
Action | Wait until the Restart timeout value is exceeded. Otherwise, contact IBM Support. |
Explanation | The server failed to restart too many times. |
Action | See the log files for possible reasons why the server could not be restarted. |
Explanation | The server failed a health check, but restarts are disabled. |
Action | See the log files for possible reasons why the server failed the health check. |
Explanation | The response time cannot be monitored. |
Action | Verify that the cell is fully sychronized and the node group exists. In the administrative console, select System administration > Node groups. |
Explanation | The target was not added to the health policy, because it could not be found. |
Action | Verify that the cell is fully sychronized and the target member exists in the administrative console. |
Explanation | The health controller could not read the configuration repository. |
Action | Verify that no cell-wide errors reading the configuration repository exist. Otherwise, contact IBM Support. |
Explanation | The health controller cannot receive health policy updates. |
Action | Verify that the deployment manager is running. |
Explanation | The health controller could not enable listening for server configuration changes in {0}. |
Action | Contact IBM Support. |
Explanation | An error occurred starting the health configuration listener. |
Action | Review the error for possible resolutions. |
Explanation | An error occurred as the configuration change was processing. |
Action | Review the error for possible resolutions. |
Explanation | An error occurred when the health controller was disabled. |
Action | Review the error for possible resolutions. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The server has been restarted the maximum number of times consecutively, and a health condition continues to be violated. |
Action | Update the maximum number of times to restart the server, and restart the server. |
Explanation | The health controller will not restart servers on nodes that are in maintenance mode. |
Action | No action is required. |
Explanation | The health controller is configured to maintain a minimum restart interval. |
Action | No action is required. |
Explanation | The health controller will not restart the only running member of a cluster. |
Action | Start another server in the cluster. |
Explanation | A health policy has been added to the configuration repository and read by the health controller. |
Action | No action is required. |
Explanation | A health policy has been added to the configuration repository, but the health controller could not read it. |
Action | Synchronize the configuration repository with all of the nodes. Disable and re-enable the health controller. |
Explanation | A health policy has been removed from the configuration repository and the health controller. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The attribute of the health policy was modified, but a problem occurred processing the new value. |
Action | Synchronize the configuration repository with all of the nodes. Disable and re-enable the health controller. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A member was added to the health policy, but a problem occurred while processing the addition. |
Action | Synchronize the configuration repository with all of the nodes. Disable and re-enable the health controller. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The health policy requires data generated by the on demand router. Only servers in an adjacent tier to the on demand router will be represented in its data. |
Action | Do not use health policies based on on demand router data for this member. |
Explanation | The health controller could not locate the specified bulletin board. |
Action | Contact IBM Support. |
Explanation | The health controller could not be started. |
Action | Contact IBM Support. |
Explanation | The server is running long-running work, and the scheduler for this work does not permit the server restart. |
Action | No action is required. |
Explanation | The node on which the server is running is being reallocated for another type of work. The servers will be stopped. |
Action | No action is required. |
Explanation | A policy for transactional work is being applied to a server that is allocated for long-running work. |
Action | Check the policy definitions, and ensure that transactional and long-running applications are not deployed to the same targets. |
Explanation | A policy that is supported only for WebSphere servers is being applied to an other middleware server. |
Action | Check the policy definitions, and ensure that unsupported health policies are not created for other middleware servers. |
Explanation | The specified server could not be stopped. |
Action | Investigate the cause of the failure in the server log files. |
Explanation | A node agent cannot be contacted when it is not running. |
Action | Verify that the node agent is running. Restart the node agent if necessary. |
Explanation | The specified server could not be started. |
Action | Investigate the cause of the failure in the server log files. |
Explanation | The server instance could not be found. |
Action | Verify that the server still exists. |
Explanation | The server does not support automated heap dumps. |
Action | The server must run an IBM JDK on WebSphere Application Server Version 6.0.2 or later. |
Explanation | A heap dump can be found at the specified location. |
Action | Retain this file for off-line analysis and problem determination. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The health controller was unable to restart the server. |
Action | Check the log files for additional information. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An error occured attempting to complete a thread dump from the server. |
Action | Check the log files for additional information. |
Explanation | The server could not be contacted. |
Action | Check the log files for additional information. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Either the server could not be contacted, the JVM does not support the heap dump command, or the maximum number of heap dumps already exists. |
Action | Check the log files for additional information. |
Explanation | The server could not be contacted. |
Action | Check the log files for additional information. |
Explanation | The heap dumps were successfully generated for the specified server. |
Action | Retain the heap dump files for off-line analysis and problem determination. |
Explanation | Because the application placement controller cannot be contacted, the dynamic cluster member cannot be restarted. |
Action | Ensure that the application placement controller is enabled. |
Explanation | The placement controller is disabled and the minimum number of instances cannot be guaranteed. |
Action | Start the application placement controller or additional instances. |
Explanation | The application placement controller recommendation would leave too few running server instances. |
Action | Start another instance in the dynamic cluster. |
Explanation | Conditions have changed since the plan was generated for the server and the condition. |
Action | A new plan will be submitted to the task management system for approval. |
Explanation | The health controller is starting a custom task. |
Action | No action is required. |
Explanation | The custom task completed successfully. |
Action | No action is required. |
Explanation | The custom task failed to complete successfully. |
Action | No action is required. |
Explanation | The health controller is automatically placing the specified server into maintenance mode. |
Action | No action is required. |
Explanation | The health controller placed the server into maintenance mode successfully. |
Action | No action is required. |
Explanation | The health controller was unable to place the server into maintenance mode. |
Action | Check the log files for additional information. |
Explanation | The health controller was unable stop an instance in a normal manner. |
Action | Check the log files for additional information. |
Explanation | The health controller requested that a SNMP trap be sent. |
Action | No action is required. |
Explanation | An error occured while attempting to send a SNMP trap. |
Action | Check the log files for additional information. |
Explanation | Health Controller has determined a server instance needs to be stopped or started. See message WXDH1121I for additional information. |
Action | If the reaction mode is supervised, use the Admin Console Task Management panel to accept or deny the recommendation. If the reaction mode is automatic, no user action is required. |
Explanation | Health Controller has submitted a task to the Task Management subsystem. See message WXDH1120I for additional information. |
Action | If the reaction mode mode is supervised, use the Admin Console Task Management panel to accept the recommendation prior to the expiration time. If the reaction mode is automatic, no user action is required. |
Explanation | Health Controller has submitted a task to the Task Management subsystem and the task was denied. If there is a reoccurrence of the conditions that originally caused the task to be generated, a new task will be generated. |
Action | No user action is required at this time. |
Explanation | Health Controller has received user approval for previously submitted task. The task will be executed. |
Action | No user action is required at this time. |
Explanation | Health Controller has submitted a task to the Task Management subsystem and the task has expired. If there is a reoccurrence of the conditions that originally caused the task to be generated, a new task will be generated. |
Action | No user action is required at this time. |
Explanation | Health Controller will submit tasks to the Task Management subsystem from the indicated cell/node/server. |
Action | No user action is required at this time. |
Explanation | This is usually caused by a user or system component requesting the shutdown or setting of maintenance mode for a server or node. |
Action | Use the Admin Console to modify the placement of dynamic cluster instances to maintain desired service level performance. |
Explanation | This is usually caused by a user or system component requesting the shutdown or setting of maintenance mode for a server or node. |
Action | No user action is required at this time. |
Explanation | This is usually caused by a user or system component requesting the shutdown or setting of maintenance mode for a server or node. |
Action | No user action is required at this time. |
Explanation | Health Controller is attempting to start or stop a server instance. |
Action | No user action is required at this time. |
Explanation | Health Controller is attempting to start or stop a server instance. |
Action | No user action is required at this time. |
Explanation | This is usually caused by a user or system component requesting the shutdown or setting of maintenance mode for a server or node. |
Action | No user action is required at this time. |
Explanation | This is usually caused by a user or system component requesting the shutdown or setting of maintenance mode for a server or node. |
Action | Use the Admin Console to modify the placement of dynamic cluster instances to maintain desired service level performance. |
Explanation | This is usually caused by a user or system component requesting the shutdown or setting of maintenance mode for a server or node. |
Action | No user action is required at this time. |
Explanation | Thread hang detection must be enabled to provide advisory information on request timeout policies. |
Action | If advisory information regarding thread status is desired, enable hang detection for the server, remove it from the request timeout policy, and add it again. |
Explanation | No sensor data was received from the server. |
Action | Ensure that PMI is enabled on the server. |
Explanation | The permitted maximum server age has been reached. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | The server has reached the maximum number of permitted requests. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | The server is approaching its maximum memory limit. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | The server is responding too slowly to incoming requests. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | A significant decrease in response time and increase in routing weight has been observed on the server. |
Action | Investigate the ODR log files and the log files for the specified server for the cause of the symptoms. |
Explanation | The server is experiencing a large number of request timeouts. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | Based on memory usage trends, a memory leak is suspected. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | A significant change in response time has been observed for one or more servlets. |
Action | Investigate the ODR log files and the log files for the specified server for the cause of the symptoms. |
Explanation | A significant increase in response time has been observed for the server. |
Action | Investigate the cause of the increase. |
Explanation | A significant change in the average EJB method response time has been observed for one or more EJBs. |
Action | Investigate the ODR log files and the log files for the specified server for the cause of the symptoms. |
Explanation | The server is experiencing a large number of request timeouts, and threads might be hung. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | A custom health condition violation has been detected. |
Action | Restart the server or specify a custom action. |
Explanation | The server is responding too slowly to incoming requests. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | The server is experiencing a large number of request timeouts. |
Action | If the policy is supervised, check the runtime tasks to approve the configured response. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | A detailed list of all health management controller states. |
Action | First review task management for potential remedies, otherwise contact IBM support. |
Explanation | An unexpected error occured. |
Action | Review the log files where the health controller is running. |