Explanation | DCS could not log a message properly. |
Action | Please report to IBM Service. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | Contact IBM Service. |
Explanation | An unexpected state has occurred. The situation is recoverable. |
Action | If situation reoccurs frequently contact IBM service |
Explanation | An unusual state has occurred. Logging this information may help in debug situations. |
Action | No action required. |
Explanation | DCS check discovered that it did not get CPU time slice for a long period of time. |
Action | Check load on machine. If the root cause cannot be determined, contact IBM service. |
Explanation | DCS stack started |
Action | None. Informational message. |
Explanation | General message for tracking important view change events |
Action | None. Informational |
Explanation | Unreadable message received from another member. This might indicate incompatible software version. |
Action | Check software version. |
Explanation | DCS Started a new transport infrastructure instance. |
Action | None. An informational message only. |
Explanation | DCS Linked to an existing transport infrastructure instance. |
Action | None. An informational message only. |
Explanation | DCS failed to create its transport infrastructure. |
Action | Contact IBM service. |
Explanation | DCS failed to join a multicast group address. A possible cause for this problem is a configured system limit on the maximal number of multicast groups. |
Action | Check network/firewall configuration of the operating system. |
Explanation | DCS failed to join a multicast group address. A possible cause for this problem is a configured system limit on the maximal number of multicast groups. |
Action | Check network/firewall configuration of the operating system. |
Explanation | The DCS Transport infrastructure on this member failed to send a UDP datagram. |
Action | Check the network connectivity of this machine. |
Explanation | DCS received a connection request, which was initiated by a member who is not part of the defined set. |
Action | None. An informational message only. |
Explanation | DCS received a new connection, which was initiated by a defined member. |
Action | None. An informational message only. |
Explanation | All new view members sent a notification to this member using the new view identifier. |
Action | None. An informational message only. |
Explanation | DCS received a connection request from a member whose address conflicts with that of the local configuration. |
Action | None. An informational message only. |
Explanation | The DCS outgoing messages queue exceeded its allocated memory limit. Further outgoing messages will be blocked. |
Action | No action required. Consider decreasing load on this process or increasing total memory available for DCS. |
Explanation | The DCS outgoing messages queue is close to exceed its allocated memory limit. |
Action | No action required. Consider decreasing load on this process or increasing total memory available for DCS. |
Explanation | The DCS outgoing messages queue is back to its normal limit. This is printed after either DCSV1003W or DCSV1004W. |
Action | None. An informational message only. |
Explanation | The transport infrastructure incoming messages memory exceeds its nominal memory limit. |
Action | Consider increasing the nominal memory size in the transport configuration or lowering the load of the specified sender. |
Explanation | The incoming message queue is back to its normal limit. This is printed after DCSV1011W. |
Action | None. An informational message only. |
Explanation | An inconsistent internal state was detected in the transport infrastructure. See the exception for more information about the root cause of the problem. |
Action | Correct the cause of the problem or contact IBM Service. |
Explanation | DCS received a token with a length that exceeds the configured maximum topic length. |
Action | Correct the maximum topic length configuration parameter. |
Explanation | Another member closed its outgoing connection to the local member. This indicates a problem with the suspected member or with connectivity. |
Action | Check the suspected member. |
Explanation | DCS failed to receive a heartbeat from another member within a configured time interval. This may indicate a problem with the suspected member or with connectivity. |
Action | Check the suspected member. |
Explanation | The outgoing connection to another member was closed. This indicates a problem with the suspected member or with connectivity. |
Action | Check the suspected member. |
Explanation | A packet sent by another member was lost. |
Action | contact IBM Service. |
Explanation | DCS failed to receive a confirmation from another member about the new view. This indicates a problem with the suspected member or with connectivity. |
Action | Check the suspected member. |
Explanation | A new view with a disconnected member has been established. |
Action | No action required. If this message repeats, please report to IBM service. |
Explanation | Another member does not include the local member in the new view members. |
Action | Check the suspected member. |
Explanation | Another member created an additional outgoing connection to the local member. This may indicate that the suspected member has been restarted or that two members use the same name. |
Action | Check the suspected member. |
Explanation | A new view with a denied member has been established. |
Action | No action required. If this message repeats, please report to IBM service. |
Explanation | The local member failed to establish the new view with the suspected member. |
Action | Check the suspected member. |
Explanation | The receiver side memory of the transport infrastructure was exhausted. In order to free memory the sender which consumes the most memory was suspected. |
Action | Consider increasing the dynamic memory size in the transport infrastructure configuration or lowering the load of the suspected member. |
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. This indicates that the suspected is either down or cannot handle the load. |
Action | Check whether the suspected member is running. If it is running, consider lowering load on the local machine or check whether the machine of the suspected member can handle the load. |
Explanation | The synchronization procedure timed out, failing to guarantee that all members are synchronized. |
Action | No action required. If this warning repeats, contact IBM service. |
Explanation | DCS received a message from an illegal sender and ignored it. |
Action | No action required. If this warning repeats, contact IBM service. |
Explanation | The synchronization procedure completed successfully. |
Action | None. An informational message only. |
Explanation | The amount of memory available for synchronization is low. |
Action | In case a DCSV2006I message does not follow in a reasonable amount of time, consider increasing DCS memory or lowering the load on the group. |
Explanation | The amount of memory available for synchronization is back to normal. |
Action | None. An informational message only. |
Explanation | DCS received an inconsecutive message from other member. |
Action | No action required. Please report to IBM service. |
Explanation | Another member failed to complete the synchronization procedure within the configured time. |
Action | No action required. If this warning repeats, contact IBM service. |
Explanation | DCS tracked an inconsistent synchronization related behaviour of another member. |
Action | No action required. Please report to IBM service. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | If the root cause cannot be determined and corrected, contact IBM Service. |
Explanation | The member was removed by the console |
Action | None. Informational |
Explanation | An internal inconsistency was detected. No recovery is possible. |
Action | Contact IBM Service |
Explanation | Received an administrative request for shutdown. |
Action | None. Informational message. |
Explanation | The stack is configured differently on the two processes. More information may follow in message DCSV8021W. |
Action | Check configuration of the two members. |
Explanation | The stack is configured differently on the two members |
Action | Check the problematic configuration parameter |
Explanation | The two members have different defined sets. The defined set inconsistency may be fixed automatically. |
Action | None. An informational message only. |
Explanation | A member in the defined set is configured with different address on two different members |
Action | Check and repair the problematic configuration parameter |
Explanation | Join attempt halted due to the specified reason. |
Action | None. Informational. If this reoccurs frequently look at root cause and/or contact IBM service. |
Explanation | Join attempt halted due to timeout waiting for a response from a member. |
Action | None. Informational. If this reoccurs frequently contact IBM service. |
Explanation | Join attempt ignored; member is already involved in a view change. After view change join may be attempted again. |
Action | None. Informational |
Explanation | A view change has completed |
Action | None. Informational |
Explanation | Defined set changed in stack |
Action | None. Informational |
Explanation | Defined set changed in stack |
Action | None. Informational |
Explanation | Internal view change protocol in process, with failed members being excluded |
Action | None. Informational |
Explanation | Internal view change protocol in process |
Action | None. Informational |
Explanation | Defined set changed in stack, however some failures |
Action | None. Informational |
Explanation | Defined set change request failed. The can be due to the timeliness of the request |
Action | None. Informational |
Explanation | Received request to install a new view in a data stack. |
Action | None. Informational |
Explanation | Received request to change the defined set. |
Action | None. Informational |
Explanation | HA Manager state was updated. |
Action | None. Informational. |
Explanation | Failed to deserialize HA Manager state. |
Action | Contact IBM Service. |
Explanation | Failed to serialize HA Manager state. |
Action | Contact IBM Service. |
Explanation | This member was suspected by another member. Automatic reply is to suspect the sender. |
Action | No action required. Check the suspected member and/or the communication between the suspected member and this member. |
Explanation | The suspect sent a message out of protocol sequence. |
Action | No action required. If problem persists contact IBM |
Explanation | Another member did not respond within expected time period. Member is removed from view and processing continues. |
Action | No action required. Check the suspected member and/or the communication between the suspected member and this member. |
Explanation | The member was suspected due to suspicion by another member. |
Action | No action required. Check the suspected member and/or the communication between the suspected member and this member. |
Explanation | Received administrative request to remove the member from view. |
Action | None. Informational |
Explanation | All other members will be removed from view due to an inconsistency |
Action | No action required. If this warning reoccurs frequently contact IBM |
Explanation | Failed to start because of illegal configuration values. |
Action | Change the transport configuration parameters. |
Explanation | Failed to create a socket. This may indicate a host network configuration problem. For example, trying to create a multicast socket when multicast is disabled on the host. |
Action | Check the exception message. |
Explanation | Failed to set the interface on the multicast socket. This may indicate a wrong configured interface address. |
Action | Check the configured local interface address. |
Explanation | Failed to set the Time-To-Live parameter on the multicast socket. |
Action | Contact IBM Service. |
Explanation | Failed to join a multicast group address. This may indicate of a multicast network configuration problem. A possible cause for this problem is a configured system limit on the maximal number of multicast groups. |
Action | Check network/firewall configuration of the operating system. |
Explanation | Failed to leave a multicast group address. This may indicate of a multicast network configuration problem. |
Action | Check network/firewall configuration of the operating system. |
Explanation | Failed to allocate enough memory to deal with an incoming message. |
Action | Consider increasing the JVM memory heap size or lowering messaging rate of other transmitters. |
Explanation | Failed to encode/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 | Failed to resolve an internet address, probably because of a DNS problem. |
Action | Check the DNS environment. |
Explanation | Failed to set the buffer size on the socket. This probably indicates of a configured limitation in the operating system. This warning may lead to inferior transport performance. |
Action | Check operating system network configuration. |
Explanation | Failed to bind a socket to the specified address. This probably indicates that the specified port is already taken. |
Action | Check configuration of the server socket port. |
Explanation | Another machine sent a packet longer than the configured buffer length for incoming packets. This might indicate that another application is using RMM with a larger configured packet size or that a malicious sender attempts to send large packets to local machine. |
Action | Check identity and configuration of the specified sending machine. |
Explanation | An unexpected error occurred. See the exception stack trace for more detail. |
Action | Contact IBM Service. |
Explanation | failed to send a UDP packet because of a connectivity problem. |
Action | Check network connectivity. |
Explanation | Failed to set a socket parameter. |
Action | Check operating system network configuration. |
Explanation | received an incoming connection with a tag (queue name) that exceeds the configured maximum length. This probably indicates either a maximum topic size configuration problem or a malicious tampering with wire format. |
Action | Check the identity and the configured maximum token size of the specified sending machine. |
Explanation | A general networking problem occurred on a socket address. |
Action | Check network configuration. |