HMGR

HMGR0001I: The DCS Core Stack transport has been started for core group {0}. There are {1} members.
HMGR0002E: HA Manager services on this process were not started. This server is not a member of a core group.
HMGR0003E: Unable to export service {0}. The service was not found.
HMGR0004E: An attempt to start an HA Manager Management Bean (MBean) failed. The MBean id is {0}. The exception is {1}.
HMGR0005I: The Single Server DCS Core Stack transport has been started for core group {0}.
HMGR0006I: Starting the transport for Core Stack {0} using IP Address {1}, port {2}, transport type {3}.
HMGR0007W: An attempt to start High Availability Manager PMI statistics failed. The exception is {0}.
HMGR0008W: The high availability manager has detected that core group {0} has {1} configured processes. The recommended limit is {2}.
HMGR0020E: The configuration document {0} could not be read from the repository.
HMGR0021E: An error was encountered while processing the core group document. The exception is {0}.
HMGR0022E: An error was encountered reading a typed attribute from the configuration. The name is {0}, the value is {1} and the type is {2}. The exception is {3}.
HMGR0023E: An error was encountered reading a untyped attribute from the configuration. The name is {0}, the value is {1} and the type is {2}. The exception is {3}.
HMGR0024W: An error was encountered while looking up the IP address for the host name of a core group member. The host name is {0} and the exception is {1}.
HMGR0025W: An invalid value for an HA Manager configuration attribute was found. The document is {0}, the attribute is {1} and the value found is {2}.
HMGR0026E: An invalid value for an HA Manager configuration attribute was found. The document is {0}, the attribute is {1} and the value found is {2}.
HMGR0027W: A duplicate host to IP Address mapping has been detected. IP Address {0} has a mapping to host names {1} and {2}.
HMGR0028E: A duplicate DCS_UNICAST_ADDRESS port has been detected. Members {0} and {1} on host {2} are both configured to use port {3}.
HMGR0029E: The network configuration for process {0} has a port value of {1}.
HMGR0030E: The configuration document {0} could not be read from the repository.
HMGR0031E: A conflicting IP address and port has been detected for the DCS_UNICAST_ADDRESS end point. {0} members are configured to use the IP address and port combination of {1}.
HMGR0032I: Core group {0} is starting with a configured transport memory size of {1}.
HMGR0033I: Core group {0} is starting with a heart beat transmission interval of {1} milliseconds and a heart beat timeout of {2} milliseconds.
HMGR0034I: Core group {0} is starting with a discovery interval of {1} seconds.
HMGR0035I: Core group {0} is starting with a non-default liveness provider. The factory name is {1}.
HMGR0040I: No HA Policies were found in the core group.
HMGR0041E: An HA Policy without a name was found in the core group.
HMGR0042W: An error was encountered reading policy attributes from the configuration for policy {0}.
HMGR0043E: All HA Policies failed parsing.
HMGR0044E: An unrecoverable error was encountered while loading HA Policies. The exception is {0}.
HMGR0045W: The server list for policy {0} is empty. This policy requires at least one server.
HMGR0046E: An error occured while processing the policy configuration information. The specified PolicyFactory class {0} is not a PolicyFactory.
HMGR0047E: An error occured while processing the policy configuration information. The specified PolicyFactory class {0} was not instantiable. The exception is {1}
HMGR0048E: A failure occurred while attempting to create a default HAManager policy. The name of the policy is {0} and the exception is {1}.
HMGR0049E: A duplicate policy name was found in the configuration data. The policy name is {0}.
HMGR0060W: An error was encountered while obtaining the host and port information for server {0} on node {1}.
HMGR0061E: An error was encountered while processing the coregroup. The entry for server {0}, node {1} failed. The exception is {2}.
HMGR0062I: A DCS_UNICAST_ADDRESS end point does not exist for server {0} on node {1}.
HMGR0063W: The DCS_UNICAST_ADDRESS end point for server {0} on node {1} has an invalid value. {2} Will be used instead.
HMGR0064W: Resolution of IP Addresses for host name {0} found only the loopback address. The loopback address will be used.
HMGR0070E: An error was encountered while processing the hamanagerservice.xml document. The exception is {0}.
HMGR0071E: The coreGroupName attribute in the HAManagerService is null.
HMGR0080E: Unable to obtain a reference to the ConfigRepository. Configuration documents cannot be updated dynamically.
HMGR0081E: An error was received while reloading a configuration document. The document name is {0} and the exception is {1}.
HMGR0083E: An error was encountered merging configuration information. The element type is {0}. The exception is {1}.
HMGR0085I: This server received a message that a new core group document is available. This server is already running on that document version.
HMGR0086I: This server is updating its core group configuration. The new document version is {0}.
HMGR0087I: An unrecoverable error was encountered while merging the core group configuration. The version is {0}. The exception is {1}.
HMGR0088I: HA Policy information from the new core group configuration was not applied. There were {0} errors in the new configuration.
HMGR0089E: A configuration available message could not be delivered. The configuration version is {0} and the exception is {1}.
HMGR0090W: An attempt to update the High Availability manager configuration has failed. The required documents are not available on this node.
HMGR0091I: An outdated core group configuration was read from the repository. The current configuration is {0}. The configuration just read is {1}.
HMGR0092W: Unable to get HA Manager MBean on the Deployment Manager, object name used for query is {0}.
HMGR0093E: Unable to create an Admin Client connection to the deployment manager. Exception: {0}.
HMGR0094E: The query for MBean {0} failed.
HMGR0095I: Unable to locate any running processes for core group {0} that are not in single server mode. Core group configuration was not updated dynamically.
HMGR0096E: An error was encountered when trying to pull configuration from Deployment Manager. See exception for more information. Exception: {0}
HMGR0097E: Unknown error was encountered when trying to push configuration to core group {0}. See exception for more information. Exception: {1}
HMGR0098E: Unable to obtain a reference to the admin service.
HMGR0099E: This process received an updated configuration document from the {0} and it is no longer a member of core group {1}.
HMGR0103I: An attempt to activate or deactivate a member failed. There are no local group members for group {0}.
HMGR0105E: An attempt to activate or deactivate a member failed. There local member was not in the proper state. The group is {0}. The local member is {1} and the current state is {2}. The execution stack is {3}
HMGR0107E: An attempt to activate or deactivate a member failed. An internal failure has occurred. The group is {0} and the exception is {1}.
HMGR0108E: An unexpected internal state was encountered. The class is {0}, the method is {1} and the exception is {2}.
HMGR0109E: An unexpected exception was encountered while the HAManager was processing a callback from a using program. The class is {0}, the method is {1} and the exception is {2}.
HMGR0111E: An unexpected internal error occured during a joinGroup operation. The GroupName is {0}, the instance is {1} and the exception is {2}.
HMGR0112E: An unexpected error occurred during object Serialization. The object class is {0} and the exception is {1}.
HMGR0113E: A communication error occurred while forwarding group change information to the active coordinator. The exception is {0}.
HMGR0114E: An unexpected error occurred while forwarding group change information to the active coordinator. The exception is {0}.
HMGR0117E: Quorum on group {0} with members {1} has been lost and the process contains active HA Group members. The process must be terminated.
HMGR0119I: The GMS service has requested that the server be terminated. The reason is {0}.
HMGR0120E: An error occurred processing a callback from DCS. The method is {0}. The exception is {1}.
HMGR0121E: An error occurred sending a DCS Unicast message. The target member is {0}. The message type is {1}. The exception is {2}.
HMGR0122E: An error occurred sending a DCS Multicast message. The message type is {0}. The exception is {1}.
HMGR0123I: A GroupUpdate message was received for a group that does not exist. The group name is {0}.
HMGR0124I: An activate or deactive request for the local member of group {0} failed. The reason is {1} and the data is {2}
HMGR0125I: An activate or deactive request for the local member of group {0} failed. The reason is {1}, the data is {2} and the exception is {3}
HMGR0126I: The method {0} has been called on the HAGroup object for group {1}, but the member has already left that group.
HMGR0127I: The HA Manager has discarded a request to activate or deactivate a group member. The member is disabled. The group is {0}.
HMGR0128E: The wrong context object was passed on a callback to the AsynchOperationComplete interface. The method is {0}, the group is {1}, the context object is {2} and the expected context is {3}.
HMGR0129I: The local member of group {0} has been disabled. The reason is {1}.
HMGR0130I: The local member of group {0} has indicated that is it not alive. The JVM will be terminated.
HMGR0131I: The local member of group {0} has not responded to a health check. The JVM will be terminated.
HMGR0132I: The local member of group {0} failed to respond properly to a health check. The exception is {1}. The JVM will be terminated.
HMGR0133E: Exception constructing cluster {0}, exception {1}
HMGR0134I: Cluster {0} is waiting for quorum. Currently {1} members online. At least {2} votes of {3} votes required for quorum.
HMGR0135I: Cluster {0} has quorum.
HMGR0136I: No such cluster defined {0}
HMGR0137I: Terminate has been called on the default core stack. This is not allowed.
HMGR0138I: Terminate has been called on a core stack. The core stack {0} will be terminated.
HMGR0139I: A non-core stack event has been routed to the core stack. The event is {0}.
HMGR0140E: An event indicating that the core group membership is inconsistent was received. Recovery failed. The exception is {0}.
HMGR0141E: Sending local state information to an active coordinator failed. The exception is {0}.
HMGR0142E: An error occurred in a component called back by the High Availability Manager. The exception is {0}.
HMGR0143E: An error occurred when the High Availability Manager attempted to dispatch a thread. The exception is {0}.
HMGR0144I: Powering down suspect server {0}
HMGR0145W: The cluster {0} is now critical.
HMGR0146W: Group {0} is not scheduled for liveness checking.
HMGR0147E: An error was encountered during liveness checking. The exception is {0}.
HMGR0148I: The channel chain transport for core group {0} contains an SSL channel.
HMGR0149E: An attempt to open a connection to core group {0} has been rejected. The sending process has a name of {1} and an IP address of {2}. Global security in the local process is {3}. Global security in the sending process is {4}. The received token starts with {5}. The exception is {6}.
HMGR0150E: An attempt to create a token to secure the High Availability Manager connection failed. The exception is {0}.
HMGR0151E: A problem was encountered while updating the core group member list. The exception is {0}.
HMGR0152W: CPU Starvation detected. Current thread scheduling delay is {0} seconds.
HMGR0157E: The channel chain {0} has failed to start after {1} retries. The process will be terminated.
HMGR0158E: The attempt to power down suspect server {0} failed.
HMGR0159E: An attempt to administratively enable High Availability Group {0} failed because the member is not in the disabled state. The current member state is {1}.
HMGR0160E: An attempt to update the state of High Availability Group {0} failed because the member is in an unknown state. The current member state is {1}.
HMGR0161E: The HA Manager has been configured to use an external Failure Detection and Discovery provider. A plug-in factory class name has not been specified.
HMGR0162W: There is no thread pool specified for TCP Channel {0}. The channel may not operate properly.
HMGR0163E: The core group bridge service on this process has violated bridge rebuild protocol. Both the previous and current set of active bridges was specified as {0}.
HMGR0164E: The core group bridge service on this process has violated bridge rebuild protocol by providing membership content with no active bridges.
HMGR0165E: The core group bridge service on this process has violated bridge rebuild protocol by attempting to end a bridge rebuild period without first beginning it.
HMGR0166E: Cannot create a proxy post because {0} is a member of the local core group.
HMGR0167E: The High Availability Manager received an improper subscriber update message from the active coordinator, an unexpected {0} was encountered.
HMGR0169E: The High Availability Manager detected a state inconsistency while attempting to notify {0} subscribers, the subscription for the subject {1} has already been closed.
HMGR0170E: The High Availability Manager detected a state inconsistency with the active coordinator while processing a subscriber update message, updating {0} state in {1} mode and received unexpected {2}.
HMGR0201E: A communication exception occured while sending a message. The message type is {0}. The GroupName is {1} and the exception is {2}.
HMGR0203E: The active Coordinator was found to be in an invalid state and could not process a message. The state is {0}, the message is {1}.
HMGR0204E: The Coordinator could not process a message. The message is {0} and the exception is {1}.
HMGR0205E: The Coordinator could not process a message. The state and the message are inconstent. The state is {0} and the message is {1}.
HMGR0206I: The Coordinator is an Active Coordinator for core group {0}. The active coordinator set is {1}.
HMGR0207I: The Coordinator was previously an Active Coordinator for core group {0} but has lost leadership. The active coordinator set is {1}.
HMGR0208E: The Coordinator could not process a message. The coordinator is in FAILED state. The message is {0}.
HMGR0209E: An internal error occured while processing the policy for group {0}. The exception is {1}
HMGR0210I: Unable to run the policy for group {0}. The group may have been deleted.
HMGR0211E: Unable to create the group state aggregation object on the active coordinator for group {0} in response to a group join from server {1}. The policy for the group cannot be determined. The exception is {2}
HMGR0212I: A request to remove the group member for server {0} from the group state aggregion for group name {1} cannot be honored. The group does not currently exist.
HMGR0213E: A request to activate or deactivate a group member was made while the policy was unstable. The GroupName is {0} The policy type is {1}.
HMGR0218I: A new core group view has been installed. The core group is {0}. The view identifier is {1}. The number of members in the new view is {2}.
HMGR0219I: An unrecognized view change event was received from the DCS transport. The view identifier is {0} and the event is {1}.
HMGR0220W: A request to move the active member of a group from one server to another cannot be performed. One of the members does not exist. The member identifier is {0} and the group is {1}.
HMGR0221W: A request to activate or deactivate a member cannot be performed. The requested state is {0}, the member identifier is {1} and the group is {2}
HMGR0222W: A request to move the active member of a group from one server to another cannot be performed. The group is not stable. The group is {0}
HMGR0223W: An unrecoverable error has occurred on the DCS core stack for core group {0}. The exception is {1}.
HMGR0224E: The core group custom property {0} is out of range. Value {1} is not allowed.
HMGR0225E: A parsing error occurred for core group custom property {0}. The value is {1} and the exception is {2}.
HMGR0226I: The core stack configuration parameter {0} has been set to {1}.
HMGR0227E: The request to create a Core Group Bridge on this server has failed. The request is invalid.
HMGR0228I: The Coordinator is not an Active Coordinator for core group {0}. The active coordinator set is {1}.
HMGR0229I: A new data stack view has been installed. The view identifier is {0}. The data stack name is {1} and the number of members in the new view is {2}.
HMGR0230E: Core group bridge ownership of subject {0} is in contention between bridges {1}.
HMGR0231W: The active coordinator detected a unexpected condition while processing the {0} component of a message with {1} mode from {2}, a {3} was expected. Current state is {4}.
HMGR0232E: The active coordinator received a message from {0} indicating this process is a core group bridge; however, there are no core group bridges {1}.
HMGR0233E: The active coordinator received a message from {0} with inconsistent {1} state for subject {2}, the post contents were {3} with {4} existing state.
HMGR0234W: The active coordinator detected that the state rebuild operation did not complete within the expected time. Waiting for state messages from the following process set: {0}.
HMGR0235W: The core group member {0} reported a problem. The member reporting the problem logged the reason using message {1}.
HMGR0301W: No policy was located for the group named {0}
HMGR0302W: Multiple policies match the group named {0}, Matching Policies are {1}
HMGR0401E: Creation of data stack {0} failed. The exception is {1}.
HMGR0402E: Sending a message on the data stack {0} failed. The exception is {1}.
HMGR0403E: Data stack {0} invoked the call back method {1} and it failed. The exception is {2}.
HMGR0404E: The data stack {0} could not process a received message. The message is {1} and the exception is {2}.
HMGR0405E: The data stack {0} detected an unknown event. The unrecognized event is {1}.
HMGR0406E: The data stack {0} encountered an unexpected exception calling method {1}. The exception is {2}.
HMGR0407E: A request data command on synchronous data stack {0} failed. The exception is {1}.
HMGR0408E: The synchronous data stack {0} encountered an unexpected exception processing method {1}. The exception is {2}.
HMGR0501E: Encountered an abnormal termination of the internal data stack named {0}.
HMGR0502E: An error occurred while using the internal data stack named {0}. The exception is {1}.
HMGR0503I: The message path of the internal data stack named {0} is highly congested.
HMGR1000E: An attempt to create an Agent instance of type {0} in AgentClass {1} failed. The exception is {2}
HMGR1001W: An attempt to receive a message of type {0} for Agent {1} in AgentClass {2} failed. The exception is {3}
HMGR1002W: AgentClass {0} has been notified that a request to add a secondary Agent {1} has completed. There is no record of that request. The execution stack is {2}
HMGR1003W: Method {0} for AgentClass {1} was called unexpectedly. The execution stack is {2}
HMGR1004W: Method {0} for Agent {1} was called unexpectedly. The execution stack is {2}
HMGR1005E: A problem has been detected while attempting to send a message of type {0} for Agent {1}. The exception is {2}
HMGR1006W: A problem has been detected while attempting to send a message of type {0} for Agent {1}. The exception is {2}
HMGR1007E: A problem has been detected while attempting to send a message of type {0} for Agent {1}. The exception is {2}
HMGR1008E: An attempt to destroy the primary instance of Agent {0} failed. The exception is {1}
HMGR1009E: An attempt to destroy a secondary instance of Agent {0} failed. The exception is {1}
HMGR1012E: An attempt to register AgentClass {0} with the agent framework has failed. The exception is {1}
HMGR1013E: A failure occured while processing a membership change for Agent {0}. The exception is {1}
HMGR1014E: A failure occured while processing a membership change for AgentClass {0}. The exception is {1}
HMGR1015E: An internal failure occured in an Agent. The Agent name is {0}. The exception is {1}
HMGR1016E: An internal failure occured in an AgentClass. The AgentClass name is {0}. The exception is {1}
HMGR1017I: An attempt to create a backup Agent has failed. The message could not be delivered to the target. The Agent is {0}.
HMGR1018I: An attempt to cancel creation of a backup Agent has failed. The AgentClass does not have a request scheduled for Agent {0}.
HMGR1019W: This process received a message that does not map to an AgentClass channel or to any known Agent channel. The channel name from message is {0}. The sender is {1}. The local AgentClass channel is {2}. The known local Agent Channels are [{3}].
HMGR1105I: Group {0} active member moved to {1} in {2} milliseconds
HMGR1106I: An out of specification group was found while processing the policy for group {0}. Too many members are active.
HMGR1107I: Unable to make group consistent with the specified policy. There are no available members to activate. The group name is {0}. The exception is {1}.
HMGR1108I: Unable to make group consistent with the specified policy. There are no available members to activate. The group name is {0}.
HMGR1109I: Unable to make group consistent with the specified policy. There are no available members to deactivate. The group name is {0}.
HMGR1200I: HA Manager administrative action requested. Operation is "{0}".
HMGR1201I: HA Manager administrative action requested. Operation is "{0}", the group is "{1}".
HMGR1202I: HA Manager administrative action requested. Operation is "{0}", the member is "{1}", the group is "{2}".
HMGR1203I: HA Manager administrative action requested. Operation is "{0}", current active member is "{1}", requested active member is "{2}", the group is "{3}".
HMGR1225W: The Administrative request could not be completed because the specified group does not exist. The request is "{0}" and the group name is "{1}".
HMGR1226W: The Administrative request could not be completed because the specified member does not exist. The request is "{0}" the member is "{1}", the group is "{2}"
HMGR1227W: The Administrative request could not be completed because the core group membership is not stable. The request is "{0}", the member is "{1}" and the group name is "{2}".
HMGR1228W: The Administrative request could not be completed because the specified member or group is not in the correct state. The request is "{0}", the member is "{1}" and the group name is "{2}". Reason = "{3}".
HMGR1300E: {0} parameter is null.
HMGR1301E: No active coordinators for core group {0} could be found.
HMGR1302E: View is changing. Retry command after the view has stabilized.
HMGR1303E: A send message problem has occurred.
HMGR1304E: The GroupName parameter must specify a group governed by a {0} policy.
HMGR1305E: The specified group does not exist.
HMGR1306E: The specified member {0} does not exist.
HMGR1307E: The member {0} is not in {1} state.
HMGR1308E: An unexpected failure occurred.
HMGR1309E: The group name string is invalid.
HMGR1310E: The MBean operation did not complete within {0} seconds.
HMGR2000I: An unusual event occurred while sending local state to the {0} manager. The exception is {1}.
HMGR2001E: An error occurred while sending local state to the {0} manager. The exception is {1}.
HMGR2002E: For the manager set named {0}, the partitioned manager group method {1} received an exception from the partitioned manager event handling method {2}. The exception is {3}. The partitioned manager group member will relinquish its membership in the underlying high-availability manager group.
HMGR2003E: Partitioned manager group received an inbound message which does not contain a valid header. The header is either absent or malformed.
HMGR2004E: Partitioned manager group received an inbound message associated with the {0} header. The header is not an existing manager set name.
HMGR2005I: Corresponding to the manager set named {0}, the partitioned manager group event handler application of group {1} has indicated that is it not alive. The JVM will be terminated.
HMGR2006E: For the manager set named {0}, the partitioned manager group failed to receive state messages from {1}
HMGR3000E: A failure occured while adding server {0} on node {1} to core group {2}. The exception is {3}.
HMGR3001E: A failure occured while removing server {0} on node {1} from core group {2}. The exception is {3}.
HMGR3002E: An unexpected condition was encountered during this admin task. The class is {0}, the method is {1} and internal details {2}.
HMGR3100I: The HA Manager work queue statistics detected a non-default value. The new base threshold is {0}.
HMGR3101I: The work queue dump threshold changed to {0} for queue {1}. The data from threshold {2} is {3}.
HMGR5000E: An attempt to access configuration data has failed. The configuration data has not been initialized. The execution stack is {0}.
HMGR5001E: An invalid configuration action has been attempted. The execution stack is {0}.
HMGR5002E: An internal error was encountered while processing a group member state change for group name {0}. The old state was {1} and the new state was {2}.
HMGR5003E: An internal error was encountered while processing a group membership change for group name {0}. The old member was {1} and the new member was {2}.
HMGR5004E: An unexpected internal state was encountered while attempting to activate a group member. No group members exists. The group is {0} and the execution stack is {1}.
HMGR5005E: No active coordinators were found. The execution stack is {0}.
HMGR5006E: The DCS provider has not been initialized. The execution stack trace is {0}.
HMGR5007E: An attempt to use the DCS provider to send a message has failed. The execution stack trace is {0}.
HMGR5008E: A bulletin board change notification has been received, but there is no data. The execution stack trace is {0}.
HMGR5009E: The host name for a process has changed. The execution stack trace is {0}.
HMGR5010E: An attempt to reconstruct a streamed map has failed. The map has no entries. The execution stack trace is {0}.
HMGR5011E: An attempt to initialize the UserCallbacks service failed. The service is already initialized. The execution stack trace is {0}.
HMGR5012E: An internal error was encountered while processing a HAManager MBean request. The group name is {0}, the member was {1} and the member action was {2}.
HMGR5013E: An internal error was encountered. The class is {0}, the method is {1}, the local state is {2}. the cause is {3} and the stack trace is {4}.
HMGR5014E: An attempt to remove Bulletin Board posts for subject {0} failed. There are no posts for this subject.
HMGR5015E: An attempt to create a Server Power Controller failed. The class name is {0} and the exception is {1}.
HMGR5016E: An attempt to inform the controller that the servant initialization completed has failed. The exception is {0}.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.hamanager.nls.HAManagerMessages.dita
File name: com.ibm.ws.hamanager.nls.HAManagerMessages.html