Explanation | Distribution and consistency services (DCS) could not log a message 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 possible causes of this problem. |
Explanation | An internal error occurred in the distribution and consistency services (DCS). See the exception stack trace for more detail. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | An unexpected internal programming state has occurred. The situation may have been automatically corrected. |
Action | If the situation reoccurs frequently, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | An unusual programming state has occurred. This information might be useful for interpreting other DCS error messages. |
Action | No action required. |
Explanation | A DCS check discovered that a runnable thread was required to wait for an excessively long time before it was dispatched to the CPU. |
Action | Check the load on the machine. Try to reduce the workload by freeing resources, such as memory and CPU utilization. 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 additional information. |
Explanation | DCS stack started |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) stack failed to start |
Action | Check the connectivity between this member and other members. |
Explanation | This message is issued to help track important view change events |
Action | No action required. |
Explanation | An unreadable message was received from another member. This problem might indicate incompatible software versions. |
Action | Check the versions of your software. |
Explanation | The distribution and consistency services (DCS) started a new transport infrastructure instance. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) linked to an existing transport infrastructure instance. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) failed to create its transport infrastructure instance. For example it failed to create the infrastructure for the channel framework DCS transports. |
Action | Check the log for other errors specific to the DCS transport type. If the problem cannot be resolved, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The distribution and consistency services (DCS) failed to join a multicast group address. A possible cause for this problem is a configured system limit for the maximum number of multicast groups. |
Action | Check the network and firewall configuration settings for your operating system. |
Explanation | The distribution and consistency services (DCS) failed to join a multicast group address. A possible cause for this problem is a configured system limit for the maximum number of multicast groups. |
Action | Check the network and firewall configuration settings for your operating system. |
Explanation | The distribution and consistency services (DCS) transport infrastructure for this member failed to send a UDP datagram. |
Action | Check the network connectivity of this machine. |
Explanation | The distribution and consistency services (DCS) received a connection request from a process that is currently not a member of the core group. |
Action | If this condition persists, synchronize the configuration for all nodes in the cell. It may be necessary to restart this process. |
Explanation | The distribution and consistency services (DCS) established a connection to another process which is a member of the same core group. |
Action | No action required. |
Explanation | A new view has been established. This member has received a notification from all members of the new view. |
Action | No action required. |
Explanation | An unusual network connectivity state has been detected. This may lead to an error condition in the future. The information logged in this message may be useful in analyzing other DCS error messages. |
Action | No action required. |
Explanation | An unexpected network connectivity state has occurred. The situation may be recovered automatically. |
Action | If this situation reoccurs frequently, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The distribution and consistency services (DCS) outgoing messages queue exceeded its configured memory limit. Further outgoing messages will be blocked. |
Action | If this message is logged frequently, consider decreasing the load on this process or increasing the total memory that is available to DCS. For more information see the product Information Center topic that describes how to configure a core group for replication. |
Explanation | The distribution and consistency services (DCS) outgoing messages queue is close to exceeding its configured memory limit. |
Action | If this message is logged frequently, consider decreasing the workload on this process or increasing the total memory that is available to DCS. For more information see the product Information Center topic that describes how to configure a core group for replication. |
Explanation | The distribution and consistency services (DCS) outgoing messages queue is back to its normal limit. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) transport infrastructure incoming messages queue is close to exceeding its configured memory limit. |
Action | Consider increasing the configured memory limit for the transport buffer or lowering the workload of the specified sender. For more information see the product Information Center topic that describes how to configure a core group for replication. |
Explanation | The incoming message queue is back to its normal limit. |
Action | No action required. |
Explanation | An inconsistent internal state was detected in the transport infrastructure. The exception should give 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 additional information. |
Explanation | The distribution and consistency services (DCS) received a security token with a length that exceeds the configured maximum token length. |
Action | Increase the value specified for the maximum security token length configuration parameter. |
Explanation | Another member closed its outgoing connection to the local member. The other member might have been stopped, or there might be a problem with the member or with network connectivity. |
Action | If the other member has not been stopped, check the other member for errors, and check network connectivity to the other member. |
Explanation | The distribution and consistency services (DCS) failed to receive a heartbeat from another member within the configured time interval. This message might indicate that there is a problem with the other member, or with network connectivity. |
Action | Check the other member for errors and check the network connectivity to the other member. |
Explanation | The outgoing connection to another member was closed. The other member might have been stopped, or there might be a network connectivy problem between the members. |
Action | If the other member has not been stopped, check the other member for errors and check the network connectivity to the other member. |
Explanation | A packet sent by another member was lost. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The network connection between this member and another member has been closed. The other member may have been stopped, there may be a problem with either member or there may be a problem with network connectivity. |
Action | If the other member has not been stopped, check the other member for errors and check the network connectivity to the other member. |
Explanation | A new view has been established. This member failed to receive the proper notification from the other member. This indicates a problem with the other member. |
Action | Check the other member for errors and check the network connectivity to the other member. |
Explanation | A new view has been established. A network connection to the other member does not exist. |
Action | No action required. If this message repeats, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | A new view has been established on another member. This member is not included in the new view. |
Action | Check the member that excluded this member from the new view. |
Explanation | Another member opened multiple network connections to this member. This may be an indication of network configuration problems. Two members may have the same IP Address and port configuration. |
Action | Check the host and port values in the DCS_UNICAST_ADDRESS end points for the two members. Check the IP address assignments for the hosts involved. |
Explanation | A new view has been established. The removed member is in a state that prevents it from participating in the new view. |
Action | If this message repeats, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | A new view has been established. This member was unable to send the proper notification to the other member. This indicates a communication problem between the two members. |
Action | Check both members for errors and check the network connectivity between the members. |
Explanation | The receiver side memory of the transport infrastructure is exhausted. To free memory the indicated member was removed. |
Action | Consider increasing the dynamic memory size in the transport infrastructure configuration or lowering the workload of the member that was removed. |
Explanation | The transport infrastructure suspected a member that failed to acknowledge messages at a sufficient rate. That member caused the memory, dedicated for saving outgoing unacknowledged messages, to be exhausted. The member might either be down or cannot handle its current workload. |
Action | Make sure that the indicated member is running. If it is running, consider lowering the workload on the local machine or make sure that the indicated member can handle its assigned workload. |
Explanation | The view synchronization timed out, failing to guarantee that all members will continue to be in the next view. Some members will be removed |
Action | If this warning repeats, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The distribution and consistency services (DCS) received a message from an sender that was not in the proper state and ignored it. |
Action | Verify the configuration of the member whose message was ignored. |
Explanation | View synchronization completed successfully. |
Action | No action required. |
Explanation | The amount of memory available for view synchronization is low. |
Action | If this message is logged frequently, consider decreasing the load on this process or increasing the total memory that is available to DCS. For more information see the product Information Center topic that describes how to configure a core group for replication. |
Explanation | The amount of memory available for view synchronization is back to normal. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) received an out of order message from another member. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | Another member failed to complete the view synchronization procedure within the expected time. |
Action | If this warning repeats, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The distribution and consistency services (DCS) detected that the indicated member broke the view synchronization protocol. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | 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 additional information. |
Explanation | An internal inconsistency was detected. No recovery is 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 additional information. |
Explanation | The indicated DCS stack has been stopped normally. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) stack is configured differently on the two members. More information may follow in message DCSV8021W. |
Action | Check the configuration of the two members. If the problem cannot be resolved, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The distribution and consistency services (DCS) stack is configured differently on the two members. |
Action | Check the configuration of the two members. If the problem cannot be resolved, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The two members have different core group memberships. The inconsistency may be fixed automatically. |
Action | Verify that the configuration has been synchronized across all of the nodes in the cell. If the configuration has not been synchronized across all of the nodes in the cell, manually synchronize the configuration. After the configuration stabilizes, this problem should resolve itself automatically. |
Explanation | An attempt to establish a new view with the indicated member failed. The reason will give additional information about the root cause of the failure. |
Action | If this problem reoccurs frequently, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | An attempt to establish a new view with the indicated member failed. The member failed to respond within a reasonable amount of time. This might be caused by high workloads on the involved nodes. |
Action | Check the workload on the involved nodes. If this problem reoccurs frequently, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | A view change request from the indicated member was ignored. This member is already involved in a view change. After the current view change completes, the new view change will be attempted again. |
Action | No action required. The view change will automatically be attempted again. 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 additional information. |
Explanation | A view change has completed |
Action | No action required. If this message is logged continuously, examine the logs of other members for potential problems. |
Explanation | New members were added to the core group membership for the stack. |
Action | No action required. |
Explanation | Existing members were removed from the core group membership for the stack. |
Action | No action required. |
Explanation | An internal view change protocol in process. Failed members will be excluded from the new view. |
Action | No action required. |
Explanation | An internal view change protocol in process |
Action | No action required. |
Explanation | New members were added to the core group membership for the stack. However, some failures occurred. |
Action | No action required. |
Explanation | An attempt to update the core group membership for the stack failed. The problem might be caused by the timing of the request |
Action | No action required. |
Explanation | An internal view change protocol in process. Failed members will be excluded from the new view. Because the number of failed members is large, they are not listed. Information about failures can be found in the message logs. |
Action | No action required. |
Explanation | Received request to install a new view in a data stack. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) received a request to change the core group membership set. |
Action | No action required. |
Explanation | The high availability manager state was updated. |
Action | No action required. |
Explanation | The distribution and consistency services (DCS) failed to deserialize the high availability manager 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 additional information. |
Explanation | The distribution and consistency services (DCS) failed to serialize the high availability manager 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 additional information. |
Explanation | This member was marked as failed by another member. This member will mark the other member as failed and will remove it from the view. |
Action | Check the logs for the other member to determine why it marked this member as failed. |
Explanation | The member that is being removed sent a message that was out of protocol sequence. |
Action | No action required. 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 additional information. |
Explanation | Another member did not respond within the expected time period. The other member will be removed from the view and processing will continue. |
Action | Check the logs for the other member and the communication between the two members. |
Explanation | The removed member was marked as failed by another view member. It will be removed from the view. |
Action | Check the logs for removed member and the requesting member and the network communication between them. |
Explanation | The distribution and consistency services (DCS) received an administrative request to remove the indicated member from the view. |
Action | No action required. |
Explanation | All other members will be removed from the view because of an internal inconsistency. |
Action | No action required. If this warning reoccurs frequently, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The transport layer (RMM) failed to start because of an illegal configuration value. |
Action | Change the values of the transport configuration parameters. |
Explanation | The transport layer (RMM) failed to create a socket. This problem might indicate a host network configuration problem. For example, RMM might be trying to create a multicast socket when multicast is disabled on the host. |
Action | Check the exception message. |
Explanation | The transport layer (RMM) failed to set the interface on the multicast socket. This problem might indicate an incorrectly configured interface address. |
Action | Check the configured local interface address. |
Explanation | The transport layer (RMM) failed to set the Time-To-Live parameter on the multicast socket. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The transport layer (RMM) failed to join a multicast group address. This problem might indicate that there is a multicast network configuration problem. A possible cause for this problem is a configured system limit on the maximum number of multicast groups. |
Action | Check the network and firewall configuration of the operating system. |
Explanation | The transport layer (RMM) failed to leave a multicast group address. This problem might indicate that there is a multicast network configuration problem. |
Action | Check the network and firewall configuration of the operating system. |
Explanation | The transport layer (RMM) failed to allocate enough memory to receive an incoming message. |
Action | Consider increasing the JVM memory heap size or decreasing the workload of other members. |
Explanation | The transport layer (RMM) failed to encode or decode a string because the local operating system does not support the specified encoding. |
Action | Configure the local operating system to support the specified encoding. |
Explanation | The transport layer (RMM) failed to resolve an internet address. This problem might indicate that there is a DNS problem. |
Action | Check the DNS environment. |
Explanation | The transport layer (RMM) failed to set the buffer size on the socket. This probably indicates a configured limitation in the operating system. This limitation may lead to poor transport performance. |
Action | Check the network configuration for the operating system. |
Explanation | The transport layer (RMM) failed to bind a socket to the specified address. This problem probably indicates that the specified port is already in use. |
Action | Check configuration of the server socket port. |
Explanation | Another machine sent a packet that was longer than the configured buffer length for incoming packets. This problem might indicate that another application is using RMM with a larger configured packet size or that a malicious sender attempted to send large packets to the local machine. |
Action | Check the identity and configuration of the specified sending machine. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support for additional information. |
Explanation | The transport layer (RMM) failed to send a UDP packet because of a connectivity problem. |
Action | Check the network connectivity. |
Explanation | The transport layer (RMM) failed to set a socket parameter. |
Action | Check the network configuration for the operating system. |
Explanation | The transport layer (RMM) received an incoming connection with a tag (queue name) that exceeds the configured maximum length. This problem probably indicates either a maximum topic size configuration problem or that a malicious tampering with wire format has occurred. |
Action | Check the identity and the configured maximum token size of the specified sending machine. |
Explanation | A general networking problem occurred on the indicated socket address. |
Action | Check the network configuration. |