WebSphere Process Server messages     Operating Systems: All supported

DCSV

DCSV0000W: DCS Stack {0} at Member {1}: DCS encountered an internal problem while logging. Log message details are: {2}.
Problem 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}.
Problem 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 internal programming state has occurred. Internal details: {2}. The exception is {3}.
Problem An unexpected internal programming state has occurred. The situation is recoverable.
User response If situation reoccurs frequently contact IBM service
DCSV0003I: DCS Stack {0} at Member {1}: Internal programming state information. Internal details: {2}
Problem An unusual programming state has occurred. Logging this information may be useful when other DCS error messages occur.
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.
Problem DCS check discovered that it did not get CPU time slice for a long period of time.
User response Check load on machine. Try to reduce workload by freeing resources (memory, CPU). If the root cause cannot be determined, contact IBM service.
DCSV0005I: DCS Stack {0} at Member {1}: Started. Stack version information: {2}. Stack protocol information: {3}.
Problem DCS stack started
User response None. Informational message.
DCSV0006W: DCS Stack {0} at Member {1}: Failed to establish connection. Stack version information: {2}. Stack protocol information: {3}.
Problem DCS stack failed to start
User response Check connectivity to other members .
DCSV0008I: DCS Stack {0} at Member {1}: General information message. Internal details: {2}
Problem General message for tracking important view change events
User response None. Informational message.
DCSV0009W: DCS Stack {0} at Member {1}: Received an unreadable message from member {2}. Member will be removed from view. Version details are {3}.
Problem 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}. Version information is {3}.
Problem 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}. Version information is {3}.
Problem 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}.
Problem DCS failed to create its transport infrastructure (for example: Channel Framework).
User response Check the log for other errors specific to the transport type. If the problem can't be resolved contact IBM service.
DCSV1011W: DCS Stack {0} at Member {1}: Failed to join a view due to a problem with multicast group {2}. Will not be able to receive messages from member(s) {3}.
Problem 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}: Unable to communicate with other members, due to failure to join the connected multicast group {2}.
Problem 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}: The transport infastructure failed to send a UDP datagram to address {2}. DCS Logical Channel is {3}. Exception is {4}.
Problem 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}.
Problem DCS received a connection request, which was initiated by a member who is not part of the coregroup membership.
User response If this condition persists, synchronize the configuration for this node and restart the process.
DCSV1032I: DCS Stack {0} at Member {1}: Connected a defined member {2}.
Problem 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}.
Problem All new view members sent a notification to this member using the new view identifier.
User response None. An informational message only.
DCSV1035I: DCS Stack {0} at Member {1}: Connectivity information regarding member {2}, details: {3}
Problem An unusual connectivity state has occurred. Logging this information may be useful when other DCS error messages occur.
User response None. An informational message only.
DCSV1036W: DCS Stack {0} at Member {1}: An unusual connectivity state occured with member {2}, details: {3}.
Problem An unexpected internal connectivity state has occurred. The situation is recoverable.
User response If situation reoccurs frequently contact IBM service
DCSV1051W: DCS Stack {0} at Member {1}: Raised a high severity congestion event for outgoing messages. Configured and actual memory thresholds are {2}.
Problem The DCS outgoing messages queue exceeded its allocated memory limit. Further outgoing messages will be blocked.
User response If message repeats, consider decreasing load on this process or increasing total memory available for DCS. For more information see the Information Center on configuring a core group for replication.
DCSV1052W: DCS Stack {0} at Member {1}: Raised a medium severity congestion event for outgoing messages. Configured and actual memory thresholds are {2}.
Problem The DCS outgoing messages queue is close to exceed its allocated memory limit.
User response If message repeats, consider decreasing load on this process or increasing total memory available for DCS. For more information see the Information Center on configuring a core group for replication.
DCSV1053I: DCS Stack {0} at Member {1}: Outgoing message congestion has returned to normal.
Problem 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}. Configured and actual memory thresholds are {3}.
Problem 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. For more information see the Information Center on configuring a core group for replication.
DCSV1055I: DCS Stack {0} at Member {1}: Incoming message congestion has returned to normal.
Problem 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}.
Problem 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}.
Problem 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}: Outgoing connection from the other member was closed. Member to be removed from view is: {2} . DCS logical channel is {3}.
Problem Another member closed its outgoing connection to the local member. The other member may have been stopped, or there may be a problem with the member or with network connectivity.
User response If the member has not been stopped, check the other member for errors and check network connectivity to other member.
DCSV1112W: DCS Stack {0} at Member {1}: Member {2} failed to respond to periodic heartbeats. Member will be removed from view. Configured Timeout is {3} milliseconds. DCS logical channel is {4}.
Problem DCS failed to receive a heartbeat from another member within a configured time interval. This may indicate a problem with the other member or with network connectivity.
User response Check the other member for errors and check network connectivity to other member.
DCSV1113W: DCS Stack {0} at Member {1}: Outgoing connection to the other member was closed. Member to be removed from view is {2}. DCS logical channel is {3}.
Problem The outgoing connection to another member was closed. The other member may have been stopped, or there is a problem with the other member or with network connectivity.
User response If the other member has not been stopped, check the other member for errors and check network connectivity to other member.
DCSV1114W: DCS Stack {0} at Member {1}: Packet sent by {2} was lost. DCS logical channel is {3}.
Problem A packet sent by another member was lost.
User response contact IBM Service.
DCSV1115W: DCS Stack {0} at Member {1}: Member {2} connection was closed. Member will be removed from view. DCS connection status is {3}.
Problem Another member closed its connection with the local member. The other member may have been stopped, or there may be a problem with the member or with network connectivity.
User response If the member has not been stopped, check the other member for errors and check network connectivity to other member.
DCSV1131W: DCS Stack {0} at Member {1}: Member {2} failed to confirm the establishment of a new view. The member will be removed from next view. New view identifier is {3}. Configured timeout is {4} milliseconds. DCS logical channel is {5}.
Problem DCS failed to receive a confirmation from another member about the new view. This indicates a problem with the other member or with network connectivity.
User response Check the problematic member for errors and check network connectivity to other member.
DCSV1132W: DCS Stack {0} at Member {1}: Member {2} is not connected despite the fact that the member is in the new view. The member will be removed from the next view. The new view identifier is {3}.
Problem 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}: Member {2} did not include the local member in the new view. The other member will be removed. New view identifier is {3}. DCS logical channel is {4}.
Problem Another member does not include the local member in the new view members.
User response Check the problematic member.
DCSV1134W: DCS Stack {0} at Member {1}: Member {2} established an additional connection. The member will be removed from the view. DCS logical channel is {3}.
Problem Another member created an additional outgoing connection to the local member. This may indicate that the problematic member has been restarted or that two members use the same name.
User response Check the problematic member.
DCSV1135W: DCS Stack {0} at Member {1}: Removing member {2} because it is included in the new view, yet it is denied. The new view identifier is {3}.
Problem A new view with a denied member has been established.
User response If this message repeats, please report to IBM service.
DCSV1136W: DCS Stack {0} at Member {1}: Member {2} failed to establish a connection to this member. The member will not be included in the new view. The new view identifier is {3}.
Problem The local member failed to establish the new view with the problematic member.
User response Check the problematic member.
DCSV1151W: DCS Stack {0} at Member {1}: Removing member {2} because its outgoing messaging rate is too high. The internal details are {3}.
Problem The receiver side memory of the transport infrastructure was exhausted. In order to free memory the sender which consumes the most memory will be removed.
User response Consider increasing the dynamic memory size in the transport infrastructure configuration or lowering the load of the problematic member.
DCSV1152W: DCS Stack {0} at Member {1}: Removing member {2} because it failed to acknowledge messages at a sufficient rate. The internal details are {3}.
Problem 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 problematic member might either be down or cannot handle the load.
User response Check whether the problematic 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 view synchronization procedure timed out. The configured timeout is {2}. The internal details are {3}.
Problem The view synchronization timed out, failing to guarantee that all members will continue to be in the next view, so some members will be removed
User response If this warning repeats, contact IBM service.
DCSV2002W: DCS Stack {0} at Member {1}: Received message from invalid member {2}. The message was ignored. The message is considered invalid due to {3}.
Problem DCS received a message from an invalid sender and ignored it.
User response Verify the configuration of the invalid member, either on the local member or the invalid member.
DCSV2004I: DCS Stack {0} at Member {1}: View synchronization completed successfully. The View Identifier is {2}. The internal details are {3}.
Problem View synchronization completed successfully.
User response None. An informational message only.
DCSV2005W: DCS Stack {0} at Member {1}: The amount of memory available for view synchronization is low. The configured memory size is {2} bytes. Currently used memory size is {3} bytes.
Problem The amount of memory available for view synchronization is low.
User response If a DCSV2006I message indicating that memory levels have returned to normal does not follow almost immediately, contact IBM service.
DCSV2006I: DCS Stack {0} at Member {1}: The amount of memory available for view synchronization is back to normal.
Problem The amount of memory available for view synchronization is back to normal.
User response None. An informational message only.
DCSV2101W: DCS Stack {0} at Member {1}: Member {2} sent messages in the wrong order. The current incoming message number is {3}, the previous message number is {4}. The other member will not be allowed in the next view.
Problem DCS received an out of order message from other member.
User response Please report to IBM service.
DCSV2102W: DCS Stack {0} at Member {1}: Member {2} failed to complete the synchronization procedure, and will not be allowed into the next view.
Problem Another member failed to complete the synchronization procedure within the configured time.
User response If this warning repeats, contact IBM service.
DCSV2103W: DCS Stack {0} at Member {1}: Member {2} broke the view synchronization protocol, and will not be allowed into the next view. Internal details are {3}.
Problem DCS tracked an inconsistent view synchronization related behaviour of another member.
User response Please report to IBM service.
DCSV7011E: DCS Stack {0} at Member {1}: An exception occurred during a callback to High Availability Manager. The method is {2}. The exception is {3}.
Problem 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.
DCSV8010E: DCS Stack {0} at Member {1}: An internal error was encountered while processing a view change. Internal details are {2}.
Problem An internal inconsistency was detected. No recovery is possible.
User response Contact IBM Service
DCSV8011I: DCS Stack {0} at Member {1}: Member received a request for shutdown.
Problem Member received a shutdown request and will be stopped.
User response None. Informational message.
DCSV8020W: DCS Stack {0} at Member {1}: Inconsistency of configuration with that of member {2}.
Problem The stack is configured differently on the two processes. More information may follow in message DCSV8021W.
User response Check configuration of the two members. If the problem can not be resolved contact IBM Service
DCSV8021W: DCS Stack {0} at Member {1}: The configuration is inconsistent with that of member {2}. Local configuration parameter {3} has a value of {4}, whereas the value at the inconsistent member is {5}.
Problem The stack is configured differently on the two members
User response Check configuration of the two members. If the problem can not be resolved contact IBM Service
DCSV8022I: DCS Stack {0} at Member {1}: Inconsistency of configured core group membership with that of another member. Inconsistent member is {2}. The list of members only in the local coregroup membership is {3}, whereas the list of members only in the coregroup membership at the inconsistent member is {4}.
Problem The two members have different coregroup memberships. The inconsistency may be fixed automatically.
User response Verify that the configuration has been synchronized across all the nodes in the cell. If not, manually synchronize the configuration. Once the configuration stabilizes, this problem should resolve itself automatically
DCSV8030I: DCS Stack {0} at Member {1}: Failed to join or establish a view with member {2}. The reason is {3}.
Problem Join attempt halted due to the specified reason. This may be caused by high loads on the involved nodes.
User response None. Informational. Verify load on the involved nodes. If this reoccurs frequently contact IBM service.
DCSV8031I: DCS Stack {0} at Member {1}: Failed to join or establish a view due to timeout,{2} seconds, waiting for member {3}
Problem Join attempt halted due to timeout waiting for a response from a member. This may be caused by high loads on the involved nodes.
User response None. Informational. Verify load on the involved nodes. If this reoccurs frequently contact IBM service.
DCSV8032I: DCS Stack {0} at Member {1}: Ignored attept to join a view by member {2} because the local member is not in a proper state to do a join.
Problem Join attempt ignored; member is already involved in a view change. After view change join may be attempted again.
User response None. The join will automatically be attempted again. If the problem persists, contact IBM Service.
DCSV8050I: DCS Stack {0} at Member {1}: New view installed, identifier {2}, view size is {3}
Problem A view change has completed
User response None. Informational
DCSV8051I: DCS Stack {0} at Member {1}: Core group membership set changed. Added: {2}.
Problem Core group membership set changed in stack
User response None. Informational
DCSV8052I: DCS Stack {0} at Member {1}: Core group membership set changed. Removed: {2}.
Problem Core group membership set changed in stack
User response None. Informational
DCSV8053I: DCS Stack {0} at Member {1}: View change in process. Excluded members are {2}.
Problem 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.
Problem Internal view change protocol in process
User response None. Informational
DCSV8055W: DCS Stack {0} at Member {1}: Core group membership set changed. Added: {2} Failed to add {3}.
Problem Core group membership set changed in stack, however some failures
User response None. Informational
DCSV8056I: DCS Stack {0} at Member {1}: Failed to do a core group membership set change request. Internal details are: {2}.
Problem Core group membership set change request failed. The can be due to the timeliness of the request
User response None. Informational
DCSV8057I: DCS Stack {0} at Member {1}: View change in process. Number of members excluded is {2}. For more information see the logs above.
Problem Internal view change protocol in process, with failed members being excluded. Since the number of failed members is large, they are not listed, but information regarding failures can be found in the logs
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}
Problem 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 Core group membership set. Internal details: {2}
Problem Received request to change the Core group membership set.
User response None. Informational
DCSV8070I: DCS Stack {0} at Member {1}: Updated HA Manager state. New state version is {2}
Problem 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}
Problem 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}
Problem Failed to serialize HA Manager state.
User response Contact IBM Service.
DCSV8100W: DCS Stack {0} at Member {1}: Removing member {2} from view as a response to removal by other member of local member.
Problem This member was removed by another member. Automatic response is to remove the other member (mutual suspicion).
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}: Removing member {2} from view because it broke protocol. Internal details: {3}
Problem The problematic member sent a message out of protocol sequence.
User response No action required. If problem persists contact IBM
DCSV8103W: DCS Stack {0} at Member {1}: Removing member {2} from view because the member did not respond within the timeout period of {3} seconds. Internal details: {4}.
Problem Another member did not respond within expected time period. Member is removed from view and processing continues.
User response No action required. Check the other member and/or the communication between the other member and this member.
DCSV8104W: DCS Stack {0} at Member {1}: Removing member {2} because the member was requested to be removed by member {3}. Internal details {4}
Problem The member is being removed due to request by another member.
User response No action required. Check the removed member and/or the communication between the removed member and the requesting member.
DCSV8106I: DCS Stack {0} at Member {1}: Denied member {2} because of administrative denial request. Internal details: {3}.
Problem Received administrative request to remove the member from view.
User response None. Informational
DCSV8108W: DCS Stack {0} at Member {1}: Removing all other members due to an internal inconsistency. The internal details are {2}
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem 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}.
Problem A general networking problem occurred on a socket address.
User response Check network configuration.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.dcs.common.event.nls.dcs.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)