The following sections are included in this appendix:
The following are TCMP-related log messages:
%n1 - the latency in milliseconds of the communication delay; %s - the full Member information. Severity: 2-Warning or 5-Debug Level 5 or 6-Debug Level 6 depending on the length of the delay.
%n1 - the maximum allowed latency in milliseconds; %n2 - the actual latency in milliseconds. Severity: 3-Informational or 5-Debug Level 5 depending on the message frequency.
%s1 - the cluster name; %s2 - the full Member information. Severity: 3-Informational.
%s1 - the full Member information for this node; %s2 - the cluster name; %s3 - the full Member information for the cluster senior node. Severity: 3-Informational.
%s - the full Member information for a new node that joined the cluster this node belongs to; %n - the node id of the cluster senior node. Severity: 5-Debug Level 5.
%s - the full Member information for a node that left the cluster; %n - the node id of the cluster senior node. Severity: 5-Debug Level 5.
%n - the node id of the departed node; %s - the full Member information for a node that left the cluster. Severity: 5-Debug Level 5.
%n - the senior service member id; %s - a cluster service member's id. Severity: 1-Error.
%s - the service name; %n - the senior service member id. Severity: 5-Debug Level 5.
%s1 - set of members that can communicate with the member indicated in %s2; %s2 - member that can communicate with set of members indicated in %s1. Severity: 1-Error.
Severity: 2-Warning
%s1 - the cluster member that sent the panic; %s2 - a member claiming to be the senior member. Severity 2-Warning
%s1 - the cluster senior member as known by this node; %s2 - a member claiming to be the senior member. Severity: 1-Error.
%n1 - an id of the Coherence node that joins the service; %s - the service name; %n2 - the senior node for the service. Severity: 5-Debug Level 5.
%n1 - an id of the Coherence node that joins the service; %s - the service name; %n2 - the senior node for the service. Severity: 5-Debug Level 5.
%s - the service name; %n - the number of entries in the service configuration map. Severity: 5-Debug Level 5.
%s - the full information for the TcpSocket that serves as a TcpRing connector to another node; %n - the node id to which this node has connected. Severity: 5-Debug Level 5.
%n - the node id that tries to connect to this node; %s - the full information for the TcpSocket that serves as a TcpRing connector to another node. Severity: 4-Debug Level 4.
%s1 - the full Member information for a node that this node failed to communicate with; %s2 - the full information about the "witness" nodes that are asked to confirm the suspected member departure. Severity: 2-Warning.
%n - the number of other nodes in the cluster this node was a member of. Severity: 1-Error.
%n1 - The number of seconds a packet has failed to be delivered or acknowledged; %s1 - the recipient of the packets indicated in the message; %s2 - the sender of the packets indicated in the message; %n2 - the number of seconds since a packet was delivered successfully between the two members indicated above. Severity: 2-Warning.
%s1 - Address of node attempting to join cluster; %s2 - List of WKA addresses. Severity: 1-Error.
%s - the senior node of the cluster. Severity: 2-Warning.
%n1 - the number of packets that fits in the buffer that Coherence attempted to allocate; %n2 - the size of the buffer Coherence attempted to allocate; %n3 - the number of packets that fits in the actual allocated buffer size; %n4 - the actual size of the allocated buffer. Severity: 2-Warning.
Severity: 2-Warning
%n - a stack trace. Severity: 5-Debug Level 5.
%n - the number of seconds that is specified by the packet publisher's resend timeout which is 5 minutes by default. Severity: 2-Warning.
%n - the number of seconds that is specified by the packet publisher's resend timeout which is 5 minutes by default. Severity: 2-Warning.
%s - the cluster member to which this member has joined to form a TCP-Ring. Severity: 6-Debug Level 6.
%s - the cluster member from which this member has disconnected. Severity: 6-Debug Level 6.
The following are configuration-related log messages:
%s - the full resource path (URI) of the operational configuration descriptor. Severity: 3-Informational.
%s - the URI (file or resource) of the operational configuration descriptor override. Severity: 3-Informational.
%s - the URI of the operational configuration descriptor override. Severity: 3-Informational.
%s1 - the URI of the operational configuration descriptor or override; %s2 - the name of the XML element that contains an incorrect reference URI. Severity: 1-Error.
The following are partitioned cache-related log messages:
%n1 - the node id this node asks to transfer partitions from; %n2 - the number of partitions this node is willing to take. Severity: 4-Debug Level 4.
%n1 - the number of primary partitions this node transferring to a requesting node; %n2 - the total number of primary partitions this node currently owns; %n3 - the node id that this transfer is for; %n4 - the number of partitions that the requesting node asked for. Severity: 4-Debug Level 4.
%n1 - the number of backup partitions this node transferring to a different node; %n2 - the total number of partitions this node currently owns that are "endangered" (do not have a backup); %n3 - the node id that this transfer is for; %n4 - the number of partitions that the transferee can take before reaching the "fair share" amount. Severity: 4-Debug Level 4.
%n1 - the index of the backup partition that this node transferring to a different node; %n2 - the partition number that is being transferred; %n3 the node id of the previous owner of this backup partition; %n4 the node id that the backup partition is being transferred to. Severity: 5-Debug Level 5.
%n1 the partition number for which a backup transfer was in-progress; %n2 the node id that the backup partition was being transferred to; %n3 the node id of the previous backup owner of the partition. Severity: 4-Debug Level 4.
%n1- the number of configuration updates. Severity: 5-Debug Level 5.
%n1 - the size in KB of the transfer that was limited; %n2 the number of partitions that were transferred. Severity: 4-Debug Level 4.
%n1 - the time in milliseconds before the next distribution check is scheduled. Severity: 6-Debug Level 6.
%n1 - the number of partitions being restored. Severity: 3-Informational.
%n1 the partition number whose ownership is being re-published; %n2 the node id of the primary partition owner, or 0 if the partition is orphaned. Severity: 4-Debug Level 4.
%n1 - the number of attempts made to resolve the ownership conflict; %n2 - the partition whose ownership is in dispute; %n3 - the node id of the service member in disagreement about the partition ownership; %n4 - the node id of the partition's primary owner in this node's ownership map; %n5 - the node id of the partition's primary owner in the other node's ownership map. Severity: 4-Debug Level 4.
%n1 - the number of orphaned primary partitions that were re-assigned. Severity: 2-Warning.
Severity: 1-Error.
Severity: 1-Error.
%s - the name of the cache into which insert was attempted. Severity: 1-Error.
%s - the description of the filter that failed during evaluation. Severity: 1-Error.
%s - the description of the filter that failed during event transformation. Severity: 1-Error.
%s - the stack trace for the exception that occurred during index rebuild. Severity: 1-Error.
%s - the stack trace for the exception that occurred during index update. Severity: 1-Error.
%s - the stack trace for the exception that occurred while processing a query. Severity: 1-Error.
%s1 - the classname of the BackingMapManager implementation that returned a null backing-map; %s2 - the name of the cache for which the BackingMapManager returned null. Severity: 1-Error.
%s1 - the classname of the BackingMapManager implementation that failed to create a backing-map; %s2 - the name of the cache for which the BackingMapManager failed. Severity: 1-Error.
%s1 - the classname of the BackingMapManager implementation that failed to release a backing-map; %s2 - the name of the cache for which the BackingMapManager failed. Severity: 1-Error.
%s1 - the key being modified by the cache; %s2 - the expected backing-map event from the cache operation in progress; %s3 - the actual MapEvent received. Severity: 6-Debug Level 6.
%s1 - the name of the service which has made a re-entrant call; %s2 - the name of the method on which a re-entrant call was made. Severity: 2-Warning.
%s1 - the description of the request that must be repeated; %n1 - the number of items that are outstanding due to re-distribution; %n2 - the total number of items requested; %s2 - the list of partitions that are in the process of re-distribution and for which the request must be repeated. Severity: 5-Debug Level 5.
%s - information on the service that could not be started. Severity: 1-Error.
%s - information on the service that could not be started. Severity: 1-Error.
Cause: The partition-count is changed while active persistence is enabled. The current active data is copied to the trash directory.