Explanation | The high availabilty manager communication transport has started. |
Action | No action is required. |
Explanation | The high availability manager requires that every server be a member of a core group. Since this server is not a member of a core group, the high availability manager services cannot be started. |
Action | Verify the core group configuration and determine why this server is not a member of a core group. |
Explanation | The indicated service could not be exported. Recovery was not possible. |
Action | Look for previous messages in the SystemOut.log file that contain initialization failure information. If, after analyzing these messages, you cannot determine the cause of the export problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The high availability manager management bean failed to start. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager single server communication transport has been started. |
Action | No action is required. |
Explanation | The high availability manager communication transport is starting. |
Action | No action is required. |
Explanation | The high availability manager management bean that collects PMI statistics failed to start. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | This warning message alerts the user that they need to be aware of the implications of having a large core group. Failing to due so may result in degraded WebSphere performance. |
Action | See the IBM information center for more information regarding Core group scaling considerations. |
Explanation | Either the configuration XML file could not be found, is corrupted, or there is a problem with the repository service. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The coregroup.xml configuration document contains a syntax error or has been corrupted. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The configuration state is not valid. The specified attribute could not be read. |
Action | Correct the configuration state. |
Explanation | The configuration state is not valid. The specified attribute could not be read. |
Action | Correct the configuration state. |
Explanation | The high availability manager was unable to resolve the IP address for the indicated host. Either the host is unknown or has mappings to duplicate IP addresses. |
Action | See the description of the specified exception for more information. Correct the host name lookup problem and retry. |
Explanation | The specified attribute value is not valid. A default value has been assigned. |
Action | Correct the specified attribute value. |
Explanation | The specified attribute value is not valid. A default value has been assigned. |
Action | Correct the specified attribute value. |
Explanation | An IP Address that maps to multiple hosts is unusual. The duplicate mapping might be intentional and required to support another product such as the IBM Edge Server. |
Action | If the duplicate mapping is unintentional, correct the mapping. If the mapping is intentional, configure the DCS_UNICAST_ADDRESS endpoints for all processes in the core group to use a specific, unique IP Address. |
Explanation | Multiple processes on the same host cannot be configured to use the same port. |
Action | Correct the problem by changing the port assignment for one of the core group members. |
Explanation | The port specified for this process is not valid. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | Either the configuration XML file could not be found, or is corrupted, or there is a problem with the repository service. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | Multiple core group members that share the same IP address and port were detected. However, each core group member must have a unique IP address and port combination. |
Action | Correct the problem by assigning a different port to each of the conflicting core group members. |
Explanation | The core group transport memory size has been changed from the default setting. |
Action | No action is required. Informational only. |
Explanation | The core group heart beating has been changed from the default setting. |
Action | No action is required. Informational only. |
Explanation | The core group discovery interval has been changed from the default setting. |
Action | No action is required. Informational only. |
Explanation | The core group liveness provider has been changed from the default setting. |
Action | No action is required. Informational only. |
Explanation | The core group configuration read by this server did not contain any high availability policies. |
Action | No action is required. |
Explanation | All high availability policies must have a unique name. |
Action | Assign the policy a unique name. |
Explanation | The configuration state is not valid. The high availability manager could not read the attributes for a high availability policy. |
Action | Correct the configuration state. |
Explanation | High availability policies were located in the core group but none of the policies could be successfully parsed. |
Action | Correct the configuration state. |
Explanation | See the description of the specified exception for more information about the root cause of the problem. |
Action | Correct the cause of the problem. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The server list for the specified policy is empty. |
Action | Correct the configuration state. |
Explanation | The name of the policy factory specified in the configuration data is incorrect. |
Action | Enter a valid name for the policy factory class. |
Explanation | The name of the policy factory specified in the configuration data is incorrect. |
Action | Either the policy factory name is entered incorrectly or that policy factory class is not available on this server. Determine which of these situations has occurred, and correct the problem. |
Explanation | An internal initialization error occurred. See the description of the exception for more information. |
Action | Look for previous messages in the SystemOut.log file that contain initialization failure information. If, after analyzing these messages, you cannot determine the cause of the export problem,See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for additional help in determining the cause of this problem. |
Explanation | Two policy definitions were found that have the same name. Each policy definition must have a unique name. |
Action | Assign a different name to one of the policies. This name must be unique from any other policy name. |
Explanation | The serverindex.xml file for the specified node appears to be out of date. |
Action | If the problem does not resolve itself, perform a full resynchronize from the master repository. |
Explanation | An incorrect server entry exists in the core group configuration document. |
Action | See the description of the specified exception for more information about what caused the problem, and correct the problem. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for additional help in determining the cause of this problem. |
Explanation | This end point is required and should be allocated when the process is created. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A null or empty string was found. Valid values include the host name, a textual IP address, or *. |
Action | Enter the proper host name in the DCS_UNICAST_ADDRESS field. |
Explanation | There might be a problem with the host name or domain name service (DNS) name resolution. Under normal circumstances, a non-loopback address is expected. |
Action | Correct the host name or the DNS name resolution problem. |
Explanation | The hamanagerservice.xml configuration document contains a syntax error or has been corrupted. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The coreGroupName attribute must be set to the core group with which this server is associated. Null is not allowed. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unknown problem exists with the ConfigRepository management bean definition table. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The specified configuration document has an unknown problem. |
Action | Scan the SystemOut.log file for error messages relating to failures in loading this configuration document. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for additional help in determining the cause of this problem. |
Explanation | The coregroup.xml configuration document contains a syntax error or has been corrupted. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The server is already using the new core group document. |
Action | No action is required. |
Explanation | The core group document is being updated. |
Action | No action is required. |
Explanation | The high availability manager encountered an unrecoverable error while updating the core group configuration settings. |
Action | Synchronize the configuration to the node in question, then restart the server. If synchronizing the configuration does not solve the problem, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for additional help in determining the cause of this problem. |
Explanation | Policy errors are tolerated when the configuration is read, but these errors prevent policy information from being updated. |
Action | Scan the SystemOut.log file for information related to the parsing errors and correct the errors. |
Explanation | The core group configuration could not be updated correctly. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The core group configuration could not be updated correctly. |
Action | Manually synchronize the configuration from the master repository on the deployment manager. Application servers on the affected node might need to be recycled. |
Explanation | The core group configuration might not have been updated correctly. |
Action | No action is required. |
Explanation | Unable to get the HA Manager MBean on the Deployment Manager. |
Action | Verify that the Deployment Manager is running, otherwise contact IBM Service. |
Explanation | Unable to create an Admin Client connection to the deployment manager. |
Action | Contact IBM Service. |
Explanation | Malformed ObjectName exception encountered. |
Action | Contact IBM Service. |
Explanation | The Deployment Manager was unable to locate any HAManager MBeans on a process that is not running in single server mode for the specified core group. |
Action | Ignore this message if there are no running processes, or if all running processes are in single server mode. Otherwise ensure that node agents are running when performing configuration changes. |
Explanation | An error was encountered when trying to pull configuration from the Deployment Manager, this process may be running on old configuration data. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | An unknown error was encountered when trying to push configuration to a core group member, the core group did not receive new configuration data. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service. |
Explanation | Unable to obtain a reference to the admin service. |
Action | Contact IBM Service. |
Explanation | This process was given an updated configuration document and it was removed from the core group it was started in. |
Action | Synchronize the nodeagent that this process is located on with the deployment manager. After synchronization, restart this process. |
Explanation | An activate or deactivate message was received but there are no local members in the group to activate or deactivate. This situation can occur under normal conditions, depending on the timing of messages. For example when members are leaving a group, one of them could receive an activate message that was sent just before that member left. |
Action | No action is required. |
Explanation | An inconsistent internal state was detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An inconsistent internal state was detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An inconsistent internal state was detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A problem occurred while processing an application callback. |
Action | A programming error by a high availability manager user is probably the cause of this problem. Use the information in the message to find and correct the root cause of the problem. If you cannot determine the root cause of the problem, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected internal error occurred. See the description of the specified exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected internal error occurred. See the description of the specified exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A message could not be sent because of a failure in the communication stack. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A message could not be sent because of an unrecoverable error. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A cluster member that contains quorum sensitive groups has lost quorum but has active members. The process must be terminated. |
Action | Restart the failed servers or correct the network partition. |
Explanation | The Group Membership Service (GMS) requested termination. The GMS should have logged the reason for this request. |
Action | No action is required. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unusual situation has occured. This situation might be the result of message latency. |
Action | No action is required. |
Explanation | A group member failed to perform the requested action. The group member will be disabled. |
Action | No action is required. |
Explanation | A group member failed to perform the requested action. The group member will be disabled. |
Action | No action is required. |
Explanation | An unusual condition was detected. This condition might be the result of a programming error. |
Action | No action is required. |
Explanation | The policy for the specified high availability group initiated a request to activate or deactivate a group member. The high availability manager determined that the requested member is disabled. |
Action | No action is required. |
Explanation | The specified programming error was detected. |
Action | No action is required. |
Explanation | The local member of the specified core group was disabled at your request. |
Action | No action is required. |
Explanation | The JVM is being terminated because the local member of the specified group is no longer functioning properly. |
Action | No action is required. |
Explanation | The JVM is being terminated because the local member of the specified group is no longer functioning properly. |
Action | No action is required. |
Explanation | The JVM is being terminated because the local member of the specified group is no longer functioning properly. |
Action | No action is required. |
Explanation | Quorum is enabled for an unknown cluster. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The cluster has services which cannot activate without the cluster having quorum. Normally, each server has a single vote and the majority of the servers must be online for quorum. If the number of servers is even then the first server has two votes. |
Action | Start more cluster members to achieve quorum. |
Explanation | The specified cluster has quorum. |
Action | No action is required. |
Explanation | This happens because if a cluster is added then its definition is pushed asynchronously to all nodes. Some nodes might not know about a cluster when other do as a result. This problem will correct itself in a few seconds. |
Action | If this persists do a manual nodesync on the problem nodes, if this fails then see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | Only the high availability manager can terminate the default core group stack. |
Action | No action is required. |
Explanation | The specified core stack has been shut down. |
Action | No action is required. |
Explanation | The core stack received an event that is not a core stack event. The specified event is ignored. |
Action | No action is required. |
Explanation | The core group membership could not be updated correctly. |
Action | Synchronize the configuration to the node in question, then restart the server. If synchronizing the configuration does not solve the problem, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The group state could not be synchronized correctly. |
Action | If the problem does not resolve by itself, stop the server and then start the server again. If the problem still exists, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The called component did not detect that an error occurred. |
Action | Use the stack trace to determine which component failed, and perform diagnostics for that component. For additional help in determining why the component failed, see the problem determination information on the WebSphere Application Server Support Web page. |
Explanation | An unrecoverable thread dispatch error occurred. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager has determined that the specified server, which is hosting a member of a critical cluster, has failed. The server is being shutdown to allow safe failover. |
Action | Check the server to determine why it failed. If you can fix the problem, start the server again so it can rejoin the cluster. |
Explanation | This specified cluster is currently online but the loss of one more cluster members will cause it to terminate. |
Action | Bring one or more of the other cluster members online or use the administrative console to remove the offline cluster members from the cluster. Lowering the number of servers that are part of the cluster lowers the number of cluster members that must remain active in order to achieve quorum. |
Explanation | An internal inconsistency was detected. This inconsistency might affect failover for the indicated group. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager encountered an error while verifying that core group members are alive. Further verification will not occur and failover processing might not function properly. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The specified core group is using a secure transport chain. |
Action | No action is required. |
Explanation | The high availability manager has rejected a connection attempt. |
Action | Ensure that global security is either enabled on both processes or disabled on both processes, and ensure that both the sending and receiving processes are members of the same core group. |
Explanation | An unexpected internal error has occurred. See the description of the specified exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The core group member list could not be dynamically updated. |
Action | If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | Threads are not being dispatched in a timely manner, and this may affect system stability. |
Action | Thread scheduling delays can have many different causes. High CPU utilization or low memory resulting in long garbage collection times or paging to disk are possibilities. Perform resource analysis to determine the proper course of action. This message will disappear when the thread scheduling delay has been corrected. |
Explanation | The DCS transport channel failed to start. The port that is designated for the DCS transport channel is probably not available. This situation can occur if the process was previously terminated abnormally. |
Action | Wait for the operating system to release the port and restart the process. You should also check the SystemOut.log file for other channel transport chain related messages. |
Explanation | The high availability manager has determined that the specified server, which is hosting a member of a critical cluster, has failed. An attempt to shutdown this server to allow safe failover has failed. |
Action | Try to determine why the server failed. If possible, fix the problem and start the server again so that it can rejoin the cluster. |
Explanation | A member of the specified core group is not in the disabled state. |
Action | Check the current state of the members of the specified core group, and determine which member is not in the disabled state. |
Explanation | A member of the specified core group is in an unknown state. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The external provider cannot be created because the factory class name has not been specified. |
Action | Specify the appropriate factory class name. |
Explanation | The TCP channel should have a dedicated thread pool defined for proper operation. |
Action | Create a thread pool for the specified TCP Channel and retry the operation. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal logic error has been detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An attempt to send a message failed with a exception in the communication stack. See the description of the exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. Ensure that all network communications are operating properly. If the root cause of the problem cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager has detected an internal logic error. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager has detected an internal logic error. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager has detected an internal logic error. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The coordinator in this process has been elected as an active coordinator. |
Action | No action is required. |
Explanation | The coordinator in this process is no longer an active coordinator. |
Action | No action is required. |
Explanation | The high availability manager has detected an internal logic error. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager detected an internal logic error. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | In response to a change in the state of a high availability group, the high availability manager tried to apply the policy for that group. The policy could not be applied because the high availability group currently has no members, and might have been deleted. |
Action | No action is required. |
Explanation | The policy for the specified high availability group cannot be found on the server. However, the policy was available on the server when the join was done. |
Action | No action is required. |
Explanation | The high availability manager detected an internal inconsistency. |
Action | No action is required. |
Explanation | The high availability manager detected an internal inconsistency. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | Processes have been added or removed from the existing view. |
Action | No action is required. |
Explanation | The type of the event is not recognized. The high availability manager could not respond to the view change event that it received from the DCS transport because it did not recognize the specified event type. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The identified member was not moved because it is not a member of the specified core group. |
Action | Select a member that is defined as a member of this core group, and retry the operation. |
Explanation | The specified member could not be activated or deactivated because it is already in that state. |
Action | If you need to deactivate a member, select a member that is in the active state, and retry the operation. If you need to activate a member, select a member that is in the inactive state, and retry the operation. |
Explanation | The high availability group is currently undergoing a state transition that cannot be interrupted. |
Action | Wait for the transition to complete and retry the operation. |
Explanation | An error was received from the DCS transport channel. |
Action | If the error does not resolve itself, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The specified value is not valid for this custom property. |
Action | See the product documentation to determine the values that can be specified for this custom property. |
Explanation | The specified value is not valid for this custom property. |
Action | See the product documentation to determine the values that can be specified for this custom property. |
Explanation | A core stack custom property was used to override the default value for the specified configuration parameter. |
Action | No action is required. |
Explanation | A core group bridge can only be created on a server that is part of a network deployment configuration. |
Action | Create the core group bridge on an eligible server. |
Explanation | The coordinator in this process is not an active coordinator for the specified core group. |
Action | No action is required. |
Explanation | Processes have been added or removed from the existing view. |
Action | No action is required. |
Explanation | An internal inconsistency was detected. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | This is an indication of internal state mismatch between coregroup members and should not frequently occur, the message is ignored by the active coordinator. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal inconsistency was detected. The active coordinator ignores the incoming message. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal inconsistency was detected. The active coordinator ignores the incoming message. |
Action | The root cause of the problem appears to be an internal error. See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The active coordinator was in the process of rebuilding state, but did not receive the expected state messages from all core group processes within the expected time limit. |
Action | Review the log files for the specified set of processes that failed to send state messages to determine the problem. If necessary, stop or terminate the failing processes. |
Explanation | This process received a message that another core group member has reported a problem. |
Action | For more information, locate the specified message ID in the log file for the core group member that reported the problem. If necessary, stop or terminate the failing process. |
Explanation | All groups must exactly match only one policy rule. There is no policy match for the specified high availability group. |
Action | Create a policy for the specified high availability group if a policy does not already exist for that group. |
Explanation | All groups must exactly match only one policy rule. There are multiple policies that match the specified high availability group. |
Action | Make the match sets for the other policies more specific, or delete the extra policies so that only one policy matches this high availability group. |
Explanation | An unexpected error occurred while creating the data stack. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected error occurred attempting to send a data stack message. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The data stack implementation detected a failure invoking a method on the registered call back class. See the description of the exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager encountered a problem while trying to process a received data stack message. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager encountered an unknown data stack event. No harm was caused by this condition. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected data stack exception occurred. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected error occurred attempting to peform a synchronous request for data. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected synchronous data stack exception occurred. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The internal data stack of the view synchronous high-availability manager group encountered an unexpected termination event. See the exception stack trace for more information. |
Action | Correct the root cause of the problem. If the root cause cannot be determined and corrected, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager detected problem with the internal data stack that is used by the partitioned managed group. See the exception stack trace for more information. |
Action | Correct the root cause of the problem. If the root cause cannot be determined and corrected, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The message path of the internal data stack that is used by the partitioned managed group has reached its upper congestion limit. |
Action | No action is required. |
Explanation | There are several reasons why an attempt to create an agent might have failed, including application errors, configuration problems, and internal errors. See the description of the specfied exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | This failure is unexpected. Secondary agents might not have been created or destroyed, as expected. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager detected the indicated internal inconsistency. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager detected the indicated internal inconsistency. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager detected the indicated internal inconsistency. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager detected the indicated internal inconsistency. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager encountered a communication problem. The high availability manager will try to resend the message. |
Action | Ensure that all network paths are operating properly. |
Explanation | The high availability manager encountered an unknown or unexpected problem while attempting to send a message. See the description of the exception for more information. |
Action | Examine the stack trace to determine the root cause of the problem and correct it. If the root cause cannot be determined or is due to an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | There are several reasons why an attempt to destroy the primary instance of an agent might have failed, including application errors, configuration problems and internal errors. See the description of the exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error or a configuration error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | When a primary agent is destroyed, the secondary agents associated with the primary are also destroyed. There are several reasons why an attempt to destroy the secondary agents might have failed, including application errors, configuration problems and internal errors. See the description of the exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error or a configuration error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | There are several reasons why an attempt to to register the specified AgentClass might have failed, including application errors, configuration problems and internal errors. See the description of the exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error or a configuration error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | There are several reasons why a failure might have occurred while processing a membership change for the specified agent, including application errors, configuration problems and internal errors. See the description of the exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error or a configuration error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | There are several reasons why a failure might have occurred while processing a membership change for the specified agent, including application errors, configuration problems and internal errors. See the description of the exception for more information. |
Action | Use the associated exception name, message and stack trace to determine the root cause of the failure. If the root cause is an application error or a configuration error, correct the cause of the failure and retry the operation. If the root cause is an internal error, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal failure occured in the specified agent. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal failure occured in the specified AgentClass. See the description of the exception for more information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The high availability manager encountered a communication problem while trying to send a message to the target. The high availability manager will try to resend the message. |
Action | Ensure that all network paths are operating properly. |
Explanation | The high availability manager detected the indicated internal inconsistency. |
Action | No action is required. |
Explanation | A message was sent via the high availability manager Agent framework and received by this member. However, the channel name included in the message does not match any existing AgentClass or Agent channel name. It is possible for this to occur if the receiving component associated with the channel name in the message was removed while the message was in flight. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The HAManager MBean migrateActiveMember operation was used to move the active member. The move was completed in the specified time. |
Action | No action is required. |
Explanation | While performing policy processing, the high availability manager discovered that more members of the specified high availability group are active then should be active. |
Action | No action is required. If this message frequently reoccurs, check previous messages for the original source of the problem. |
Explanation | While performing policy processing, the high availability manager discovered that the specified high availability group is not consistent with its policy. The high availability manager tried to correct the problem, but was unable to make the high availability group consistent with its policy. |
Action | No action is required. If this message frequently reoccurs, check previous messages for the original source of the problem. |
Explanation | While performing policy processing, the high availability manager discovered that the specified high availability group is not consistent with its policy. The high availability manager tried to correct the problem, but was unable to make the high availability group consistent with its policy. |
Action | This is probably a temporaty condition that will be resolved when current high availability group members reach a stable state. If the problem persists, check for problems with the component that is associated with the high availability group name. |
Explanation | While performing policy processing, the high availability manager discovered that the specified high availability group is not consistent with its policy. The high availability manager tried to correct the problem, but was unable to make the high availability group consistent with its policy. |
Action | This is probably a temporaty condition that will be resolved when current high availability group members reach a stable state. If the problem persists, check for problems with the component that is associated with the high availability group name. |
Explanation | The specified high availability manager administrative action was requested. |
Action | No action is required. |
Explanation | The specified high availability manager administrative action was requested. |
Action | No action is required. |
Explanation | The specified high availability manager administrative action was requested. |
Action | No action is required. |
Explanation | The specified high availability manager administrative action was requested. |
Action | No action is required. |
Explanation | An asynchronous administrative operation was requested, and during background processing, the specified high availability group could not be found. Therefore, no action was taken. |
Action | Retry the failing command with a valid GroupName parameter. |
Explanation | An asynchronous administrative operation was requested, and during background processing, the specified high availability group member could not be found. Therefore, no action was taken. |
Action | Retry the failing command with valid NodeName and ServerName parameters. |
Explanation | An asynchronous administrative operation was requested, and during background processing, the high availability manager determined that the core group membership is changing. Therefore, no action was taken. |
Action | Because of the timing of asynchronous operations, it is normal for the high availability manager to occasionally encounter this situation. Wait for the servers in this core group to enter a steady state (are either in a started or stopped state) and retry the command that failed. |
Explanation | An asynchronous administrative operation was requested, and during background processing, it was determined that the specified high availability member or high availability group is not in the correct state for the requested action. Therefore, no action was taken. |
Action | Because of the timing of asynchronous operations, it is normal for the high availability manager to occasionally encounter this situation. Verify that the current state of the high availability member or high availability group, and if necessary, retry the command that failed. |
Explanation | A high availability manager MBean operation detected a null parameter. |
Action | Check the product documentation for the correct settings for the specified paramenter, and retry the command. |
Explanation | A high availability manager MBean operation could not be completed because no active coordinator could be found for the core group. |
Action | Verify that at least two of the servers that are members of this core group are running. If two servers are running, check their messages log files for additional messages that might indicate a problem. |
Explanation | A high availability manager MBean operation could not be completed because the view is changing. The view might be changing because servers are being started, or servers have been stopped or have failed. |
Action | Wait for the core group view to stabilize and then retry the command. |
Explanation | A problem has occurred while attempting to send a message to the active coordinator. |
Action | Retry the command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The policy for the specified high availability group is not of the required type. |
Action | Specify the name of a high availability group that is associated with the indicated policy type as the value for the GroupName parameter, and retry the command. |
Explanation | The name specified for the GroupName parameter does not match any existing high availability groups. |
Action | Specify a valid high availability group name for the GroupName parameter, and retry the command. |
Explanation | The specified Node and ServerName parameters do not match any existing high availability group members. |
Action | Specify a valid member and retry the command. |
Explanation | The high availability manager MBean operation cannot be performed because the indicated member is not in the required state. |
Action | Either wait for the member to reach the required state, and then retry this command, or specify a different high availability group member when you issue the command. |
Explanation | During processing of a high availability manager MBean, an unexpected error condition occurred. |
Action | Retry the failing command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The specified high availability group name must be either a comma delimited string of name=value pairs, or an asterisk character. |
Action | Specify a valid group name, a valid subset of a group name, or an asterisk character, and retry the command. |
Explanation | The high availability manager did not receive a response to a MBean operation within the time limit set for a JMX command. |
Action | Retry the failing command. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The intended partitioned manager group receiver member, might have already left the high availability group. |
Action | No action is required. |
Explanation | An unexpected error occurred. See the exception stack trace for more information. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A partitioned manager event handling method passed an unhandled exception to the partitioned manager group. See the exception stack trace for more information. |
Action | The partitioned manager group member has been terminated. If you want this instance of partitioned manager group to be functional, stop and restart it. |
Explanation | The partitioned manager group received an inbound state distribution or application message containing header information that is not valid. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A partitioned manager group received an inbound state distribution or application message that is associated with an unexpected header. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The partitioned manager group event handler application has requested process termination. |
Action | No action is required. |
Explanation | The partitioned manager group expected state messages from other members but never received them. |
Action | Correct the root cause of the problem. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The specified server was not added to the indicated core group. See the exception stack trace for more information. |
Action | Correct the root cause of the problem and retry the operation. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | The specified server was not removed from the indicated core group. See the exception stack trace for more information. |
Action | Correct the root cause of the problem and retry the operation. If the root cause cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected internal error occurred. See the description of the specified exception for more information. |
Action | Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, see the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | HA Manager detected that the JVM property websphere.hamanager.workqueue.threshold is configured for this process. |
Action | An informational message. No action required. |
Explanation | HA Manager detected that the work queue dump threshold changed. |
Action | An informational message. No action required. |
Explanation | An inconsistent internal state was detected. The requested configuration data could not be accessed. Processing cannot continue. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An inconsistent internal state was detected. The requested configuration change could not be made. Processing cannot continue. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal inconsistency was detected. The member state change could not be completed. No recovery was possible. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal inconsistency was detected. The high availability group membership change was not processed. No recovery was possible. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An inconsistent internal state was detected. No group member was activated because there were no members defined for this high availability group. Processing should not continue. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An inconsistent internal state was detected. Processing should not continue. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A distribution and consistency services (DCS) operation was requested, but the DCS provider has not been initialized. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A distribution and consistency services (DCS) send message operation was requested, but the caller has no identity. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A bulletin board operation failed. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A configuration update operation failed. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | A streamed map could not be reconstructed. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An initialization operation failed. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An internal inconsistency was detected. The high availability manager MBean request could not be processed. No recovery was possible. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unexpected condition occurred. |
Action | Check the stack trace for a message that may help indicate the cause of the problem. If the problem cannot be solved, contact IBM Service. |
Explanation | An inconsistent internal state has been detected. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unrecoverable error has been detected. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |
Explanation | An unrecoverable error has been detected. |
Action | See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem. |