DCS messages

DCSV0000W: DCS Stack {0} at Member {1}: DCS encountered an internal problem while logging. Log message details are: {2}.
Explanation: DCS could not log a message properly.
User Response: Please report to IBM Service.

DCSV0001E: DCS Stack {0} at Member {1}: An internal error occurred in DCS. The exception is {2}. Method is {3}.
Explanation: An unexpected error occurred. See the exception stack trace for more detail.
User Response: Contact IBM Service.

DCSV0002W: DCS Stack {0} at Member {1}: An unexpected programming state has occurred. Internal details: {2}. The exception is {3}.
Explanation: An unexpected state has occurred. The situation is recoverable.
User Response: If situation reoccurs frequently contact IBM service

DCSV0003I: DCS Stack {0} at Member {1}: An unusual programming state has occurred. Internal details: {2}
Explanation: An unusual state has occurred. Logging this information may help in debug situations.
User Response: No action required.

DCSV0004W: DCS Stack {0} at Member {1}: Did not receive adequate CPU time slice. Last known CPU usage time at {2}. Inactivity duration was {3} seconds.
Explanation: DCS check discovered that it did not get CPU time slice for a long period of time.
User Response: Check load on machine. If the root cause cannot be determined, contact IBM service.

DCSV0005I: DCS Stack {0} at Member {1}: Started
Explanation: DCS stack started
User Response: None. Informational message.

DCSV0008I: DCS Stack {0} at Member {1}: General info message. Internal details: {2}
Explanation: General message for tracking important view change events
User Response: None. Informational

DCSV0009W: DCS Stack {0} at Member {1}: Suspected another member upon receiving an unreadable message from the other member. Suspected member is {2}. Internal details are {3}.
Explanation: Unreadable message received from another member. This might indicate incompatible software version.
User Response: Check software version.

DCSV1001I: DCS Stack {0} at Member {1}: Created a new transport infrastructure instance successfully. Transport type is {2}.
Explanation: DCS Started a new transport infrastructure instance.
User Response: None. An informational message only.

DCSV1002I: DCS Stack {0} at Member {1}: Linked to an existing transport infrastructure instance. Transport type is {2}.
Explanation: DCS Linked to an existing transport infrastructure instance.
User Response: None. An informational message only.

DCSV1003E: DCS Stack {0} at Member {1}: Failed to create transport infrastructure. Transport type is {2}.
Explanation: DCS failed to create its transport infrastructure.
User Response: Contact IBM service.

DCSV1011W: DCS Stack {0} at Member {1}: Failed to join multicast group {2}. Will not be able to receive messages from member {3}.
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.
User Response: Check network/firewall configuration of the operating system.

DCSV1012E: DCS Stack {0} at Member {1}: Failed to join the connected multicast group {2}. Will not be able to communicate with other members.
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.
User Response: Check network/firewall configuration of the operating system.

DCSV1013W: DCS Stack {0} at Member {1}: RMM Failed to send a UDP datagram to address {2}. DCS Logical Channel is {3}. Exception is {4}.
Explanation: The DCS Transport infrastructure on this member failed to send a UDP datagram.
User Response: Check the network connectivity of this machine.

DCSV1031I: DCS Stack {0} at Member {1}: Received a connection from an undefined member {2}. Source address is {3}.
Explanation: DCS received a connection request, which was initiated by a member who is not part of the defined set.
User Response: None. An informational message only.

DCSV1032I: DCS Stack {0} at Member {1}: Connected a defined member {2}.
Explanation: DCS received a new connection, which was initiated by a defined member.
User Response: None. An informational message only.

DCSV1033I: DCS Stack {0} at Member {1}: Confirmed all new view members in view identifier {2}. View channel type is {3}.
Explanation: All new view members sent a notification to this member using the new view identifier.
User Response: None. An informational message only.

DCSV1034W: DCS Stack {0} at Member {1}: Received a connection from a member {2} with an inconsistent address. Expected the configured address {4} but got {3} instead.
Explanation: DCS received a connection request from a member whose address conflicts with that of the local configuration.
User Response: None. An informational message only.

DCSV1051W: DCS Stack {0} at Member {1}: Raised a high severity congestion event for outgoing messages. Internal details are {2}.
Explanation: The DCS outgoing messages queue exceeded its allocated memory limit. Further outgoing messages will be blocked.
User Response: No action required. Consider decreasing load on this process or increasing total memory available for DCS.

DCSV1052W: DCS Stack {0} at Member {1}: Raised a medium severity congestion event for outgoing messages. Internal details are {2}.
Explanation: The DCS outgoing messages queue is close to exceed its allocated memory limit.
User Response: No action required. Consider decreasing load on this process or increasing total memory available for DCS.

DCSV1053I: DCS Stack {0} at Member {1}: Outgoing messages congestion state is back to normal.
Explanation: The DCS outgoing messages queue is back to its normal limit. This is printed after either DCSV1003W or DCSV1004W.
User Response: None. An informational message only.

DCSV1054W: DCS Stack {0} at Member {1}: Raised a medium severity congestion event for incoming messages. The sender that requires most memory is {2}. Internal details are {3}.
Explanation: The transport infrastructure incoming messages memory exceeds its nominal memory limit.
User Response: Consider increasing the nominal memory size in the transport configuration or lowering the load of the specified sender.

DCSV1055I: DCS Stack {0} at Member {1}: Incoming messages congestion state is back to normal.
Explanation: The incoming message queue is back to its normal limit. This is printed after DCSV1011W.
User Response: None. An informational message only.

DCSV1071E: DCS Stack {0} at Member {1}: Transport infrastructure internal error. Exception is {2}.
Explanation: An inconsistent internal state was detected in the transport infrastructure. See the exception for more information about the root cause of the problem.
User Response: Correct the cause of the problem or contact IBM Service.

DCSV1072E: DCS Stack {0} at Member {1}: Received token from HA Manager that exceeds the configured maximum token length. Received token length is {2}. Configured maximum length is {3}.
Explanation: DCS received a token with a length that exceeds the configured maximum topic length.
User Response: Correct the maximum topic length configuration parameter.

DCSV1111W: DCS Stack {0} at Member {1}: Suspected another member because the outgoing connection from the other member was closed. Suspected members is {2}. DCS logical channel is {3}.
Explanation: Another member closed its outgoing connection to the local member. This indicates a problem with the suspected member or with connectivity.
User Response: Check the suspected member.

DCSV1112W: DCS Stack {0} at Member {1}: Suspected member {2} because of heartbeat timeout. Configured Timeout is {3} milliseconds. DCS logical channel is {4}.
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.
User Response: Check the suspected member.

DCSV1113W: DCS Stack {0} at Member {1}: Suspected another member because the outgoing connection to the other member was closed. Suspected member is {2}. DCS logical channel is {3}.
Explanation: The outgoing connection to another member was closed. This indicates a problem with the suspected member or with connectivity.
User Response: Check the suspected member.

DCSV1114W: DCS Stack {0} at Member {1}: Suspected member {2} because a packet sent by {2} was lost. DCS logical channel is {3}.
Explanation: A packet sent by another member was lost.
User Response: contact IBM Service.

DCSV1131W: DCS Stack {0} at Member {1}: Suspected member {2} because it failed to confirm the establishment of a new view. New view identifier is {3}. Configured timeout is {4} milliseconds. DCS logical channel is {5}.
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.
User Response: Check the suspected member.

DCSV1132W: DCS Stack {0} at Member {1}: Suspected member {2} because it is included in the new view, yet it is not connected. The new view identifier is {3}.
Explanation: A new view with a disconnected member has been established.
User Response: No action required. If this message repeats, please report to IBM service.

DCSV1133W: DCS Stack {0} at Member {1}: Suspected another member because the other member did not include the local member in the new view. Suspected member is {2}. New view identifier is {3}. DCS logical channel is {4}.
Explanation: Another member does not include the local member in the new view members.
User Response: Check the suspected member.

DCSV1134W: DCS Stack {0} at Member {1}: Suspected another member upon receiving an additional connection from the other member. Suspected member is {2}. DCS logical channel is {3}.
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.
User Response: Check the suspected member.

DCSV1135W: DCS Stack {0} at Member {1}: Suspected member {2} because it is included in the new view, yet it is denied. The new view identifier is {3}.
Explanation: A new view with a denied member has been established.
User Response: No action required. If this message repeats, please report to IBM service.

DCSV1136W: DCS Stack {0} at Member {1}: Suspected another member after failing to establish a connection to the other member for a new view. Suspected member is {2}. The new view identifier is {3}.
Explanation: The local member failed to establish the new view with the suspected member.
User Response: Check the suspected member.

DCSV1151W: DCS Stack {0} at Member {1}: Suspected another member because its outgoing messaging rate is too high. Suspected member is {2}. The internal details are {3}.
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.
User Response: Consider increasing the dynamic memory size in the transport infrastructure configuration or lowering the load of the suspected member.

DCSV1152W: DCS Stack {0} at Member {1}: Suspected member {2} because it failed to acknowledge messages at a sufficient rate. The internal details are {3}.
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.
User Response: 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.

DCSV2001W: DCS Stack {0} at Member {1}: The synchronization procedure timed out. The configured timeout is {2}. The internal details are {3}.
Explanation: The synchronization procedure timed out, failing to guarantee that all members are synchronized.
User Response: No action required. If this warning repeats, contact IBM service.

DCSV2002W: DCS Stack {0} at Member {1}: Message from illegal member {2} was ignored. The reason is {3}.
Explanation: DCS received a message from an illegal sender and ignored it.
User Response: No action required. If this warning repeats, contact IBM service.

DCSV2004I: DCS Stack {0} at Member {1}: The synchronization procedure completed successfully. The View Identifier is {2}. The internal details are {3}.
Explanation: The synchronization procedure completed successfully.
User Response: None. An informational message only.

DCSV2005W: DCS Stack {0} at Member {1}: The amount of memory available for synchronization is low. The configured memory size is {2} bytes. Currently used memory size is {3} bytes.
Explanation: The amount of memory available for synchronization is low.
User Response: 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.

DCSV2006I: DCS Stack {0} at Member {1}: The amount of memory available for synchronization is back to normal.
Explanation: The amount of memory available for synchronization is back to normal.
User Response: None. An informational message only.

DCSV2101W: DCS Stack {0} at Member {1}: Suspected member {2} because it sent an inconsecutive message. The current incoming message number is {3}, whereas the previous message number is {4}.
Explanation: DCS received an inconsecutive message from other member.
User Response: No action required. Please report to IBM service.

DCSV2102W: DCS Stack {0} at Member {1}: Suspected member {2} because it failed to complete the synchronization procedure.
Explanation: Another member failed to complete the synchronization procedure within the configured time.
User Response: No action required. If this warning repeats, contact IBM service.

DCSV2103W: DCS Stack {0} at Member {1}: Suspected member {2} because it broke the synchronization protocol. Internal details are {3}.
Explanation: DCS tracked an inconsistent synchronization related behaviour of another member.
User Response: No action required. Please report to IBM service.

DCSV7011E: DCS Stack {0} at Member {1}: An error occurred during a callback to High Availability Manager. The method is {2}. The exception is {3}.
Explanation: An unexpected error occurred. See the exception stack trace for more detail.
User Response: If the root cause cannot be determined and corrected, contact IBM Service.

DCSV7012I: DCS Stack {0} at Member {1}: member {2} administratively denied
Explanation: The member was removed by the console
User Response: None. Informational

DCSV8010E: DCS Stack {0} at Member {1}: An internal error was encountered while processing a view change. Internal details are {2}.
Explanation: An internal inconsistency was detected. No recovery is possible.
User Response: Contact IBM Service

DCSV8011I: DCS Stack {0} at Member {1}: Member is being shutdown following an administrative request.
Explanation: Received an administrative request for shutdown.
User Response: None. Informational message.

DCSV8020W: DCS Stack {0} at Member {1}: Inconsistency of configuration with that of member {2}.
Explanation: The stack is configured differently on the two processes. More information may follow in message DCSV8021W.
User Response: Check configuration of the two members.

DCSV8021W: DCS Stack {0} at Member {1}: Inconsistency of configuration with another member. Inconsistent member is {2}. Local configuration parameter {3} has a value of {4}, whereas the value at the inconsistent member is {5}.
Explanation: The stack is configured differently on the two members
User Response: Check the problematic configuration parameter

DCSV8022I: DCS Stack {0} at Member {1}: Inconsistency of configured defined set with that of another member. Inconsistent member is {2}. The list of members only in the local defined set is {3}, whereas the list of members only in the defined set at the inconsistent member is {4}.
Explanation: The two members have different defined sets. The defined set inconsistency may be fixed automatically.
User Response: None. An informational message only.

DCSV8023W: DCS Stack {0} at Member {1}: Inconsistency of configured defined set addresses with another member. Inconsistent member is {2}. The address of member {3} at the inconsistent member is {5}, whereas in the local defined set the address is {4}.
Explanation: A member in the defined set is configured with different address on two different members
User Response: Check and repair the problematic configuration parameter

DCSV8030I: DCS Stack {0} at Member {1}: Failed a join attempt with member {2}. The reason is {3}.
Explanation: Join attempt halted due to the specified reason.
User Response: None. Informational. If this reoccurs frequently look at root cause and/or contact IBM service.

DCSV8031I: DCS Stack {0} at Member {1}: Failed join attempt due to timeout,{2} seconds, waiting for member {3}
Explanation: Join attempt halted due to timeout waiting for a response from a member.
User Response: None. Informational. If this reoccurs frequently contact IBM service.

DCSV8032I: DCS Stack {0} at Member {1}: Ignored join attempt by member {2} because the local member is not in a proper state to do a join.
Explanation: Join attempt ignored; member is already involved in a view change. After view change join may be attempted again.
User Response: None. Informational

DCSV8050I: DCS Stack {0} at Member {1}: New view installed, identifier {2}, view size is {3}
Explanation: A view change has completed
User Response: None. Informational

DCSV8051I: DCS Stack {0} at Member {1}: Defined set changed. Added: {2}.
Explanation: Defined set changed in stack
User Response: None. Informational

DCSV8052I: DCS Stack {0} at Member {1}: Defined set changed. Removed: {2}.
Explanation: Defined set changed in stack
User Response: None. Informational

DCSV8053I: DCS Stack {0} at Member {1}: View change in process. Excluded members are {2}.
Explanation: Internal view change protocol in process, with failed members being excluded
User Response: None. Informational

DCSV8054I: DCS Stack {0} at Member {1}: View change in process.
Explanation: Internal view change protocol in process
User Response: None. Informational

DCSV8055W: DCS Stack {0} at Member {1}: Defined set changed. Added: {2} Failed to add {3}.
Explanation: Defined set changed in stack, however some failures
User Response: None. Informational

DCSV8056I: DCS Stack {0} at Member {1}: Failed to do a defined set change request. Internal details are: {2}.
Explanation: Defined set change request failed. The can be due to the timeliness of the request
User Response: None. Informational

DCSV8060I: DCS Data Stack {0} at Member {1}: Received request for a new view. Current view identifier: {2}. Request to add: {3}. Request to remove: {4}. Internal details: {5}
Explanation: Received request to install a new view in a data stack.
User Response: None. Informational

DCSV8063I: DCS Stack {0} at Member {1}: Received request to change the defined set. Internal details: {2}
Explanation: Received request to change the defined set.
User Response: None. Informational

DCSV8070I: DCS Stack {0} at Member {1}: Updated HA Manager state. New state version is {2}
Explanation: HA Manager state was updated.
User Response: None. Informational.

DCSV8071W: DCS Stack {0} at Member {1}: Failed to deserialize HA Manager state. Internal details: {2}
Explanation: Failed to deserialize HA Manager state.
User Response: Contact IBM Service.

DCSV8072W: DCS Stack {0} at Member {1}: Failed to serialize HA Manager state. Version is {2}
Explanation: Failed to serialize HA Manager state.
User Response: Contact IBM Service.

DCSV8100W: DCS Stack {0} at Member {1}: Suspected member {2} as a response to suspicion by member {2} of member {1}.
Explanation: This member was suspected by another member. Automatic reply is to suspect the sender.
User Response: No action required. Check the suspected member and/or the communication between the suspected member and this member.

DCSV8102W: DCS Stack {0} at Member {1}: Suspected member {2} because of broken protocol. Internal details: {3}
Explanation: The suspect sent a message out of protocol sequence.
User Response: No action required. If problem persists contact IBM

DCSV8103W: DCS Stack {0} at Member {1}: Suspected member {2} because the member did not respond within the timeout period of {3} seconds. Internal details: {4}.
Explanation: Another member did not respond within expected time period. Member is removed from view and processing continues.
User Response: No action required. Check the suspected member and/or the communication between the suspected member and this member.

DCSV8104W: DCS Stack {0} at Member {1}: Suspected member {2} because the member is suspected by member {3}. Internal details {4}
Explanation: The member was suspected due to suspicion by another member.
User Response: No action required. Check the suspected member and/or the communication between the suspected member and this member.

DCSV8106I: DCS Stack {0} at Member {1}: Denied member {2} because of administrative denial. Internal details: {3}.
Explanation: Received administrative request to remove the member from view.
User Response: None. Informational

DCSV8108W: DCS Stack {0} at Member {1}: Suspected all other members due to an inconsistency. The internal details are {2}
Explanation: All other members will be removed from view due to an inconsistency
User Response: No action required. If this warning reoccurs frequently contact IBM

DCSV9403E: Received an illegal configuration argument. Parameter {0}, value: {1}. Exception is {2}.
Explanation: Failed to start because of illegal configuration values.
User Response: Change the transport configuration parameters.

DCSV9404E: Failed to create socket. Port is {0}. Exception is {1}.
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.
User Response: Check the exception message.

DCSV9405E: Failed to set Multicast interface {0}. Exception is {1}.
Explanation: Failed to set the interface on the multicast socket. This may indicate a wrong configured interface address.
User Response: Check the configured local interface address.

DCSV9407E: Failed to set multicast Time-To-Live to {0}. Exception is {1}.
Explanation: Failed to set the Time-To-Live parameter on the multicast socket.
User Response: Contact IBM Service.

DCSV9408W: Failed to join multicast group {0}. Exception is {1}.
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.
User Response: Check network/firewall configuration of the operating system.

DCSV9409W: Failed to leave multicast group {0}. Exception is {1}.
Explanation: Failed to leave a multicast group address. This may indicate of a multicast network configuration problem.
User Response: Check network/firewall configuration of the operating system.

DCSV9410W: Failed to allocate memory: {0} bytes. Exception is {1}.
Explanation: Failed to allocate enough memory to deal with an incoming message.
User Response: Consider increasing the JVM memory heap size or lowering messaging rate of other transmitters.

DCSV9411E: Encoding {0} not supported on this host. Exception is {1}.
Explanation: Failed to encode/decode a String because the local operating system does not support the specified encoding.
User Response: Configure the local operating system to support the specified encoding.

DCSV9412W: Failed to resolve internet address {0}. Exception is {1}.
Explanation: Failed to resolve an internet address, probably because of a DNS problem.
User Response: Check the DNS environment.

DCSV9413W: Failed to set buffer size on the socket to {0}. Internal details are {1}. Exception is {2}.
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.
User Response: Check operating system network configuration.

DCSV9414E: Failed to bind a socket to address {0}. Exception is {1}.
Explanation: Failed to bind a socket to the specified address. This probably indicates that the specified port is already taken.
User Response: Check configuration of the server socket port.

DCSV9415W: Received packet larger than configured buffer length {0} from RMM address {1}. Exception is {2}.
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.
User Response: Check identity and configuration of the specified sending machine.

DCSV9416E: An internal error occurred. Exception is {0}.
Explanation: An unexpected error occurred. See the exception stack trace for more detail.
User Response: Contact IBM Service.

DCSV9417W: Failed to send a UDP packet to address:port {0}. The exception is {1}.
Explanation: failed to send a UDP packet because of a connectivity problem.
User Response: Check network connectivity.

DCSV9419W: Failed to set socket parameter {0} to {1}. Exception is {2}.
Explanation: Failed to set a socket parameter.
User Response: Check operating system network configuration.

DCSV9420W: Received an incoming connection with a tag that exceeds the configured maximum length. Source address is {0}. Length of the received tag is {1}. Configured maximum tag length is {2}. Exception is {3}.
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.
User Response: Check the identity and the configured maximum token size of the specified sending machine.

DCSV9421W: General networking problem occurred on socket address {0}. Exception is {1}.
Explanation: A general networking problem occurred on a socket address.
User Response: Check network configuration.