WebSphere Process Server messages     Operating Systems: All supported

HMGR

HMGR0001I: The DCS Core Stack transport has been started for core group {0}. There are {1} members.
Problem The HA Manager communication transport has been started
User response None. Informational entry.
HMGR0002E: HA Manager services on this process were not started. This server is not a member of a core group.
Problem This server is not a member of the core group. If this server should be a member of a core group, repair the configuration document.
User response An informational message.
HMGR0003E: Unable to export service {0}. The service was not found.
Problem The indicated service could not be exported. Recovery was not possible.
User response Look for previous messages in the log related to initialization failure and analyze them first. If the problem cannot be determined, contact IBM Service
HMGR0004E: An attempt to start an HA Manager Management Bean (MBean) failed. The MBean id is {0}. The exception is {1}.
Problem A Management Bean failed to start.
User response Contact IBM Service.
HMGR0005I: The Single Server DCS Core Stack transport has been started for core group {0}.
Problem The HA Manager communication transport has been started
User response None. Informational entry.
HMGR0006I: Starting the transport for Core Stack {0} using IP Address {1}, port {2}, transport type {3}.
Problem The HA Manager communication transport is starting.
User response None. Informational entry.
HMGR0007W: An attempt to start High Availability Manager PMI statistics failed. The exception is {0}.
Problem A Management Bean failed to start.
User response Contact IBM Service.
HMGR0020E: The configuration document {0} could not be read from the repository.
Problem The configuration xml file could not be found, is corrupted or there is a problem with the repository service.
User response Contact IBM service.
HMGR0021E: An error was encountered while processing the core group document. The exception is {0}.
Problem The core group configuration document is corrupt or contains a syntax error.
User response Contact IBM Service.
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}.
Problem An invalid configuration state was encountered. An attribute could not be read.
User response Correct the configuration state.
HMGR0023E: 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}.
Problem An invalid configuration state was encountered. An attribute could not be read.
User response Correct the configuration state.
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}.
Problem Unable to resolve the IP address for the indicated host. Either the host is unknown or has mappings only to duplicate IP addresses.
User response See the exception for more detail. Correct the host name lookup problem and retry.
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}.
Problem An invalid value for an attribute was detected. A default value has been assigned.
User response Correct the attributes value and retry.
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}.
Problem An invalid value for an attribute was detected. A default value has been assigned.
User response Correct the attributes value and retry.
HMGR0027W: A duplicate host to IP Address mapping has been detected. IP Address {0} has a mapping to host names {1} and {2}.
Problem An IP Address that maps to multiple hosts is unusual. The duplicate mapping may be intentional and required to support another product such as the IBM Edge load balancer.
User response If the duplicate mapping is unintentional, fix it. If the mapping is intentional, configure the DCS_UNICAST_ADDRESS endpoints for all processes in the core group to use a specific, unique IP Address.
HMGR0028E: A duplicate DCS_UNICAST_ADDRESS port has been detected. Members {0} and {1} on host {2} are both configured to use port {3}.
Problem Multiple processes on the same host cannot be configured to use the same port.
User response Correct the problem by changing the port assignment for one of the members.
HMGR0030E: The configuration document {0} could not be read from the repository.
Problem The configuration xml file could not be found, is corrupted or there is a problem with the repository service.
User response Contact IBM service.
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}.
Problem Multiple core group members that share the same IP address and port were detected. However, each core group member must have a unique IP address and port combination.
User response Correct the problem by assigning a different port to each of the conflicting core group members.
HMGR0040I: No HA Policies were found in the core group.
Problem The core group for this server did not contain any HA Policies when read.
User response An informational message. If no policies are assigned for the core group, no action is required.
HMGR0041E: An HA Policy without a name was found in the core group.
Problem All HA Policies must have a unique name.
User response Correct the problem by assigning a name for the policy.
HMGR0042W: An error was encountered reading policy attributes from the configuration for policy {0}.
Problem An invalid configuration state was encountered. An HA Manager policy could not be read.
User response Correct the configuration state.
HMGR0043E: All HA Policies failed parsing.
Problem HA Policies were located in the core group but none were successfully parsed..
User response Correct the configuration state.
HMGR0044E: An unrecoverable error was encountered while loading HA Policies. The exception is {0}.
Problem 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.
HMGR0045W: The server list for policy {0} is empty. This policy requires at least one server.
Problem The server list for the policy is empty.
User response Correct the configuration state.
HMGR0046E: An error occured while processing the policy configuration information. The specified PolicyFactory class {0} is not a PolicyFactory.
Problem The name of the Policy Factory specified in the configuration data is incorrect.
User response Enter a valid PolicyFactory class name.
HMGR0047E: An error occured while processing the policy configuration information. The specified PolicyFactory class {0} was not instantiable. The exception is {1}
Problem The name of the Policy Factory specified in the configuration data is incorrect.
User response Either the Policy Factory name is entered incorrectly or the Policy Factory class is not available on this server. Determine which situation has occurred and correct it.
HMGR0048E: A failure occurred while attempting to create a default HAManager policy. The name of the policy is {0} and the exception is {1}.
Problem An internal initialization error occurred.
User response Contact IBM service.
HMGR0049E: A duplicate policy name was found in the configuration data. The policy name is {0}.
Problem Two policy definitions with the same name were found. This is not allowed.
User response Assign unique names to the policies.
HMGR0060W: An error was encountered while obtaining the host and port information for server {0} on node {1}.
Problem The serverindex.xml file for the specified node appears to be out of date.
User response If the problem does not resolve itself, perform a full resynchronize from the master repository.
HMGR0061E: An error was encountered while processing the coregroup. The entry for server {0}, node {1} failed. The exception is {2}.
Problem An incorrect server entry exists in the coregroup configuration document.
User response See the exception message for more details regarding the source of the error and correct if possible. Otherwise contact IBM Service.
HMGR0062I: A DCS_UNICAST_ADDRESS end point does not exist for server {0} on node {1}.
Problem This end point is required and should be allocated when the process is created.
User response Contact IBM Service.
HMGR0063W: The DCS_UNICAST_ADDRESS end point for server {0} on node {1} has an invalid value. {2} Will be used instead.
Problem A null or empty String was found. Valid values include the host name, a textual IP address or *.
User response Enter the proper host name in this field.
HMGR0064W: Resolution of IP Addresses for host name {0} found only the loopback address. The loopback address will be used.
Problem There may be a problem with the host name or DNS resolution. Under normal circumstances, a non-loopback address is expected.
User response Fix the host name or DNS problem.
HMGR0070E: An error was encountered while processing the hamanagerservice.xml document. The exception is {0}.
Problem The hamanagerservice configuration document is corrupt or contains a syntax error.
User response Contact IBM Service.
HMGR0071E: The coreGroupName attribute in the HAManagerService is null.
Problem The coreGroupName must be set to the core group this server is associated with. Null is not allowed.
User response Contact IBM Service.
HMGR0080E: Unable to obtain a reference to the ConfigRepository. Configuration documents cannot be updated dynamically.
Problem An unknown problem exists with the ConfigRepository.
User response Contact IBM Service.
HMGR0081E: An error was received while reloading a configuration document. The document name is {0} and the exception is {1}.
Problem An unknown problem exists with a configuration document.
User response Scan the log for error messages relating to failures in loading the same document and diagnose them.
HMGR0083E: An error was encountered merging configuration information. The element type is {0}. The exception is {1}.
Problem The core group configuration document is corrupt or contains a syntax error.
User response Contact IBM Service.
HMGR0085I: This server received a message that a new core group document is available. This server is already running on that document version.
Problem The core group document is already in use.
User response An informational message.
HMGR0086I: This server is updating its core group configuration. The new document version is {0}.
Problem The core group document is being updated.
User response An informational message.
HMGR0087I: An unrecoverable error was encountered while merging the core group configuration. The version is {0}. The exception is {1}.
Problem Unrecoverable error while updating the core group.
User response Synchronize the configuration to the node in question, then restart the server. If this does not solve the problem contact IBM Support.
HMGR0088I: HA Policy information from the new core group configuration was not applied. There were {0} errors in the new configuration.
Problem Policy errors are tolerated when the configuration is read, but prevent policy information from being updated.
User response Scan the log for information related to the parsing errors and correct them.
HMGR0089E: A configuration available message could not be delivered. The configuration version is {0} and the exception is {1}.
Problem The core group configuration could not be updated correctly.
User response Contact IBM Service.
HMGR0090W: An attempt to update the High Availability manager configuration has failed. The required documents are not available on this node.
Problem The core group configuration could not be updated correctly.
User response Manually synchronize the configuration from the master repository on the Deployment Manager. Application servers on the affected node may need to be recycled.
HMGR0091I: An outdated core group configuration was read from the repository. The current configuration is {0}. The configuration just read is {1}.
Problem The core group configuration may not have been updated correctly.
User response An informational message.
HMGR0103I: An attempt to activate or deactivate a member failed. There are no local group members for group {0}.
Problem An activate or deactivate message was received but there are no local members in the group to take action on. This can happen under normal conditions depending on the timing of messages. For example when members are leaving a group, one of them could receive an activate message that was sent just before the member left.
User response An informational message only.
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}
Problem An inconsistent internal state was detected.
User response No known user actions. The root cause of the problem appears to be an internal error. Contact IBM service.
HMGR0107E: An attempt to activate or deactivate a member failed. An internal failure has occurred. The group is {0} and the exception is {1}.
Problem An inconsistent internal state was detected.
User response No known user actions. The root cause of the problem appears to be an internal error. Contact IBM service.
HMGR0108E: An unexpected internal state was encountered. The class is {0}, the method is {1} and the exception is {2}.
Problem An inconsistent internal state was detected.
User response No known user actions. The root cause of the problem appears to be an internal error. Contact IBM service.
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}.
Problem An problem occurred while processing an application callback.
User response Most likely this is caused by a programming error by the HAManager user. Use the information in the message to find and fix the root cause of the problem. If the root cause cannot be determined, contact IBM service.
HMGR0111E: An unexpected internal error occured during a joinGroup operation. The GroupName is {0}, the instance is {1} and the exception is {2}.
Problem An unexpected internal error occurred. See the included exception for more information.
User response Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service.
HMGR0112E: An unexpected error occurred during object Serialization. The object class is {0} and the exception is {1}.
Problem An unexpected internal error occurred. See the included exception for more information.
User response Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service.
HMGR0113E: A communication error occurred while forwarding group change information to the active coordinator. The exception is {0}.
Problem A message could not be sent due to a failure in the communication stack.
User response Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service.
HMGR0114E: An unexpected error occurred while forwarding group change information to the active coordinator. The exception is {0}.
Problem A message could not be sent due to an unrecoverable error.
User response Examine the stack trace to determine the cause of the exception. If the root cause of the problem cannot be determined, contact IBM service.
HMGR0117E: Quorum on group {0} with members {1} has been lost and the process contains active HA Group members. The process must be terminated.
Problem A cluster member which contained quorum sensitive groups has lost quorum but has active members. The process must be terminated.
User response Restart the failed servers or fix the network partition.
HMGR0119I: The GMS service has requested that the server be terminated. The reason is {0}.
Problem The GMS service requested termination. The GMS should have logged the reason.
User response None. Informational message.
HMGR0120E: An error occurred processing a callback from DCS. The method is {0}. The exception is {1}.
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.
HMGR0121E: An error occurred sending a DCS Unicast message. The target member is {0}. The message type is {1}. The exception is {2}.
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.
HMGR0122E: An error occurred sending a DCS Multicast message. The message type is {0}. The exception is {1}.
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.
HMGR0123I: A GroupUpdate message was received for a group that does not exist. The group name is {0}.
Problem An unusual situation has occured. This may be due to message latency.
User response None. An informational message only.
HMGR0124I: An activate or deactive request for the local member of group {0} failed. The reason is {1} and the data is {2}
Problem A group member failed to perform the requested action. The group member will be disabled.
User response None. An informational message only.
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}
Problem A group member failed to perform the requested action. The group member will be disabled.
User response None. An informational message only.
HMGR0126I: The method {0} has been called on the HAGroup object for group {1}, but the member has already left that group.
Problem An unusual condition was detected. This condition may be the result of a programming error.
User response None An informational message.
HMGR0127I: The HA Manager has discarded a request to activate or deactivate a group member. The member is disabled. The group is {0}.
Problem The policy for the group initiated a request to activate the group member. The request found that the member is disabled.
User response None An informational message.
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}.
Problem A programming error was detected.
User response None An informational message.
HMGR0129I: The local member of group {0} has been disabled. The reason is {1}.
Problem A user-requested activity has been performed.
User response None An informational message.
HMGR0130I: The local member of group {0} has indicated that is it not alive. The JVM will be terminated.
Problem A local group has requested process termination.
User response None An informational message.
HMGR0131I: The local member of group {0} has not responded to a health check. The JVM will be terminated.
Problem A local group member appears to be hung.
User response None An informational message.
HMGR0132I: The local member of group {0} failed to respond properly to a health check. The exception is {1}. The JVM will be terminated.
Problem A local group member appears to be incoherent.
User response None An informational message.
HMGR0133E: Exception constructing cluster {0}, exception {1}
Problem Quorum is enabled for unknown cluster.
User response Contact IBM.
HMGR0134I: Cluster {0} is waiting for quorum. Currently {1} members online. At least {2} votes of {3} votes required for quorum.
Problem The cluster has services which cannot activate without the cluster having quorum. Normally, each server has a single votes and the majority of the servers must be online for quorum. If the number of servers is even then the first server has 2 votes.
User response Start more cluster members to achieve quorum or use wsadmin to force quorum.
HMGR0135I: Cluster {0} has quorum.
Problem This cluster has quorum.
User response No action is needed.
HMGR0136I: No such cluster defined {0}
Problem This happens because if a cluster is added then its definition is pushed asynchronously to all nodes. Some nodes may not know about a cluster when other do as a result. This will fix itself in seconds.
User response If this persists do a manual nodesync on the problem nodes, if this fails then contact IBM.
HMGR0137I: Terminate has been called on the default core stack. This is not allowed.
Problem The default core stack for a process may only be terminated by the High Availability Manager.
User response An informational message.
HMGR0138I: Terminate has been called on a core stack. The core stack {0} will be terminated.
Problem The core stack associated with a Gateway has terminated.
User response An informational message.
HMGR0139I: A non-core stack event has been routed to the core stack. The event is {0}.
Problem The core stack received an event not designated for it. The event is ignored.
User response An informational message.
HMGR0140E: An event indicating that the core group membership is inconsistent was received. Recovery failed. The exception is {0}.
Problem The core group membership could not be updated correctly.
User response Synchronize the configuration to the node in question, then restart the server. If this does not solve the problem contact IBM Support.
HMGR0141E: Sending local state information to an active coordinator failed. The exception is {0}.
Problem The group state could not be synchronized correctly.
User response If the problem does not resolve by itself, stop and start the server. If this does not solve the problem contact IBM Support.
HMGR0142E: An error occurred in a component called back by the High Availability Manager. The exception is {0}.
Problem The called component did not detect that an error occurred.
User response Determine the failing component from the stack trace and perform diagnostics for that component, or contact IBM Support.
HMGR0143E: An error occurred when the High Availability Manager attempted to dispatch a thread. The exception is {0}.
Problem An unrecoverable thread dispatch error has occurred.
User response Contact IBM Support.
HMGR0144I: Powering down suspect server {0}
Problem This server is hosting a member of a critical cluster and was detected as failed. It is being powered down to allow safe failover.
User response Check the machine to determine why it failed and if the cause can be remedied then power it back on so it can rejoin the cluster.
HMGR0145W: The cluster {0} is now critical.
Problem This cluster is currently online but the loss of one more cluster member will cause it to panic.
User response Bring the other cluster members online or remove the offline cluster members from the cluster administratively to make the cluster non critical.
HMGR0146W: Group {0} is not scheduled for liveness checking.
Problem An internal inconsistency was detected. The inconsistency may affect failover for the indicated group.
User response Contact IBM Support.
HMGR0147E: An error was encountered during liveness checking. The exception is {0}.
Problem An error was encountered and group liveness checking cannot continue. Without liveness checking failover may not function properly.
User response Contact IBM Support.
HMGR0148I: The channel chain transport for core group {0} contains an SSL channel.
Problem The High Availability Manager is running with a secure channel chain.
User response None An informational message.
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}.
Problem The High Availability Manager has rejected a connection attempt.
User response Ensure that global security is either enabled on both processes or disabled on both processes. Ensure that both the sending and receiving processes are members of the same core group.
HMGR0150E: An attempt to create a token to secure the High Availability Manager connection failed. The exception is {0}.
Problem An unexpected internal error has occurred.
User response Contact IBM support.
HMGR0151E: A problem was encountered while updating the core group member list. The exception is {0}.
Problem The core group member list could not be dynamically updated.
User response If the problem persists, contact IBM Support.
HMGR0152W: CPU Starvation detected. Current thread scheduling delay is {0} seconds.
Problem There are too many runnable threads on the machine. Threads are not being dispatched in a timely manner. This will affect system stability.
User response Remove load from the machine until this message disappears.
HMGR0157E: The channel chain {0} has failed to start after {1} retries. The process will be terminated.
Problem The channel chain has failed to start. Most likely the necessary port is not available. This can happen if the process was previously terminated abnormally.
User response Check the log for other channel related messages. Wait for the operating system to release the port and restart the process.
HMGR0158E: The attempt to power down suspect server {0} failed.
Problem This server is hosting a member of a critical cluster and was detected as failed. An attempt to power it down to allow safe failover has failed.
User response Check the machine to determine why it failed and if the cause can be remedied then power it back on so it can rejoin the cluster.
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}.
Problem The group member is not currently in the disabled state.
User response Check the current state of the group member.
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}.
Problem The group member is in an unknown state.
User response Contact IBM Support.
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}.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0164E: The core group bridge service on this process has violated bridge rebuild protocol by providing membership content with no active bridges.
Problem An internal logic error has been detected.
User response Contact IBM service.
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.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0166E: Cannot create a proxy post because {0} is a member of the local core group.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0167E: The High Availability Manager received an improper subscriber update message from the active coordinator, an unexpected {0} was encountered.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0168E: The High Availability Manager detected a state inconsistency with the active coordinator while processing a subscriber update message, the local state had an unexpected size of {0}.
Problem An internal logic error has been detected.
User response Contact IBM service.
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.
Problem An internal logic error has been detected.
User response Contact IBM service.
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}.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0171E: The High Availability Manager detected a state inconsistency with the active coordinator while processing a subscriber update message, the version of the incoming data is {0} the previous version.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0201E: A communication exception occured while sending a message. The message type is {0}. The GroupName is {1} and the exception is {2}.
Problem An attempt to send a message failed with a exception in the communication stack. See the included exception for more information.
User response Examine the stack trace to determine the cause of the exception. Ensure that all network communications are operating properly. If the root cause of the problem cannot be determined, contact IBM service.
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}.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0204E: The Coordinator could not process a message. The message is {0} and the exception is {1}.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0205E: The Coordinator could not process a message. The state and the message are inconstent. The state is {0} and the message is {1}.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0206I: The Coordinator is an Active Coordinator for core group {0}.
Problem The coordinator in this process has been elected as an active coordinator.
User response none. An informational message.
HMGR0207I: The Coordinator was previously an Active Coordinator for core group {0} but has lost leadership.
Problem The coordinator in this process is no longer an active coordinator.
User response none. An informational message.
HMGR0208E: The Coordinator could not process a message. The coordinator is in FAILED state. The message is {0}.
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0209E: An internal error occured while processing the policy for group {0}. The exception is {1}
Problem An internal logic error has been detected.
User response Contact IBM service.
HMGR0210I: Unable to run the policy for group {0}. The group may have been deleted.
Problem A change in group state occurred that triggered the application of the policy. The group currently has no members. The group may have been deleted.
User response None. An informational message.
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}
Problem The policy for the specified group cannot be found on the server. However, it was available on the server where the join was done.
User response None. An informational message.
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.
Problem An internal inconsistency was detected. The message is logged for informational purposes only.
User response None. An informational message. Processing will continue.
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}.
Problem An internal inconsistency was detected. The message is logged for informational purposes only.
User response Contact IBM Service
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}.
Problem Processes have been added or removed from the existing view.
User response None. An informational message only.
HMGR0219I: An unrecognized view change event was received from the DCS transport. The view identifier is {0} and the event is {1}.
Problem The type of the event is not recognized. The HA Manager does not know how to respond to the event.
User response Contact IBM Service.
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}.
Problem One of the requested members is not currently a member of the group.
User response Select a member in the group and retry the operation.
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}
Problem The member selected as the source is currently not active.
User response Select the active member of the group and retry the operation.
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}
Problem The group is currently undergoing a state transition that cannot be interrupted.
User response Wait for the transition to complete and retry the operation.
HMGR0223W: An unrecoverable error has occurred on the DCS core stack for core group {0}. The exception is {1}.
Problem An error was received from the DCS Transport.
User response If the error does not resolve itself, contact IBM Service.
HMGR0224E: The core group custom property {0} is out of range. Value {1} is not allowed.
Problem The specified value is not legal.
User response Consult product documentation to determine legal values for the property.
HMGR0225E: A parsing error occurred for core group custom property {0}. The value is {1} and the exception is {2}.
Problem The specified value is not legal.
User response Correct the custom property and retry the operation.
HMGR0226I: The core stack configuration parameter {0} has been set to {1}.
Problem The default value has been overriden by using a custom property.
User response An informational message. No action required.
HMGR0227E: The request to create a Core Group Bridge on this server has failed. The request is invalid.
Problem A Core Group Bridge cannot be created on a server that is not part of a network deployment.
User response Create the Core Group Bridge on an eligible server.
HMGR0228I: The Coordinator is not an Active Coordinator for core group {0}.
Problem The coordinator in this process is not an active coordinator.
User response none. An informational message.
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}.
Problem Processes have been added or removed from the existing view.
User response None. An informational message only.
HMGR0230E: Core group bridge ownership of subject {0} is in contention between bridges {1}.
Problem An internal inconsistency was detected.
User response Contact IBM Service.
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}.
Problem This is an indication of internal state mismatch between coregroup members and should not frequently occur, the message is ignored by the active coordinator.
User response Contact IBM service.
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}.
Problem An internal inconsistency was detected. The active coordinator ignores the incoming message.
User response Contact IBM service.
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.
Problem An internal inconsistency was detected. The active coordinator ignores the incoming message.
User response Contact IBM service.
HMGR0301W: No policy was located for the group named {0}
Problem All groups must have exactly one policy rule that matches with it.
User response Make sure a policy exists for the group. Create it if it does not.
HMGR0302W: Multiple policies match the group named {0}, Matching Policies are {1}
Problem All groups must have exactly one policy rule that matches with it.
User response Make the matchsets for the other policies more specific or remove them so only one policy matches this group.
HMGR0401E: Creation of data stack {0} failed. The exception is {1}.
Problem An unexpected error occurred while creating the data stack.
User response Contact IBM Service and provide the appropriate logs.
HMGR0402E: Sending a message on the data stack {0} failed. The exception is {1}.
Problem An unexpected error occurred attempting to send a data stack message.
User response Contact IBM Service and provide the appropriate logs.
HMGR0403E: Data stack {0} invoked the call back method {1} and it failed. The exception is {2}.
Problem The data stack implementation detected a failure invoking a method on the registered call back class.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR0404E: The data stack {0} could not process a received message. The message is {1} and the exception is {2}.
Problem A problem occurred trying to process a received data stack message.
User response Contact IBM service.
HMGR0405E: The data stack {0} detected an unknown event. The unrecognized event is {1}.
Problem A unknown data stack event was encountered. No harm is caused by this condition, but it is unexpected.
User response Contact IBM service.
HMGR0406E: The data stack {0} encountered an unexpected exception calling method {1}. The exception is {2}.
Problem An unexpected data stack exception occurred.
User response Contact IBM service.
HMGR0407E: A request data command on synchronous data stack {0} failed. The exception is {1}.
Problem An unexpected error occurred attempting to peform a synchronous request for data.
User response Contact IBM Service and provide the appropriate logs.
HMGR0408E: The synchronous data stack {0} encountered an unexpected exception processing method {1}. The exception is {2}.
Problem An unexpected synchronous data stack exception occurred.
User response Contact IBM service.
HMGR0501E: Encountered an abnormal termination of the internal data stack named {0}.
Problem The internal data stack of the view synchronous high-availability manager group encountered an unexpected termination event. See the exception stack trace for more detail.
User response If the root cause cannot be determined and corrected, contact IBM Service.
HMGR0502E: An error occurred while using the internal data stack named {0}. The exception is {1}.
Problem Encountered an error while using the internal data stack of the view synchronous high-availability manager group. See the exception stack trace for more detail.
User response If the root cause cannot be determined and corrected, contact IBM Service.
HMGR0503I: The message path of the internal data stack named {0} is highly congested.
Problem The message path of the internal data stack of the view synchronous high-availability manager group has reached its upper congestion limit.
User response None. An informational message.
HMGR1000E: An attempt to create an Agent instance of type {0} in AgentClass {1} failed. The exception is {2}
Problem This failure may occur for multiple reasons, including application errors, configuration problems and internal errors. See the associated exception and exception message text.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR1001W: An attempt to receive a message of type {0} for Agent {1} in AgentClass {2} failed. The exception is {3}
Problem This failure is unexpected. Secondary agents may not have been created or destroyed, as expected.
User response Contact IBM service.
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}
Problem An internal inconsistency has been detected.
User response Contact IBM Service and provide the appropriate logs.
HMGR1003W: Method {0} for AgentClass {1} was called unexpectedly. The execution stack is {2}
Problem An internal inconsistency has been detected.
User response Contact IBM Service and provide the appropriate logs.
HMGR1004W: Method {0} for Agent {1} was called unexpectedly. The execution stack is {2}
Problem An internal inconsistency has been detected.
User response Contact IBM Service and provide the appropriate logs.
HMGR1005E: A problem has been detected while attempting to send a message of type {0} for Agent {1}. The exception is {2}
Problem An internal problem has been detected.
User response Contact IBM Service and provide the appropriate logs.
HMGR1006W: A problem has been detected while attempting to send a message of type {0} for Agent {1}. The exception is {2}
Problem A communication problem was encountered. The message will be retried.
User response Ensure that all network paths are operating properly.
HMGR1007E: A problem has been detected while attempting to send a message of type {0} for Agent {1}. The exception is {2}
Problem An unknown or unexpected problem was encountered.
User response Examine the stack trace to determine the root cause of the problem and correct it. If the root cause cannot be determined or is due to an internal error, contact IBM service.
HMGR1008E: An attempt to destroy the primary instance of Agent {0} failed. The exception is {1}
Problem This failure may occur for multiple reasons, including application errors, configuration problems and internal errors. See the associated exception and exception message text.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR1009E: An attempt to destroy a secondary instance of Agent {0} failed. The exception is {1}
Problem When a primary agent is destroyed, the secondary agents associated with the primary are also destroyed. There are multiple reasons that destroy of a secondary may fail including application errors, configuration problems and internal errors. See the associated exception and exception message text.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR1012E: An attempt to register AgentClass {0} with the agent framework has failed. The exception is {1}
Problem This failure may occur for multiple reasons, including application errors, configuration problems and internal errors. See the associated exception and exception message text.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR1013E: A failure occured while processing a membership change for Agent {0}. The exception is {1}
Problem This failure may occur for multiple reasons., including application errors, configuration problems and internal errors. See the associated exception and exception message text.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR1014E: A failure occured while processing a membership change for AgentClass {0}. The exception is {1}
Problem This failure may occur for multiple reasons., including application errors, configuration problems and internal errors. See the associated exception and exception message text.
User response Use the associated exception's name, message and stack trace to determine the root cause of the failure. If the root cause is due to application error or configuration error, correct the cause of the failure and retry the operation. If the root cause is due to an internal error, contact IBM service.
HMGR1015E: An internal failure occured in an Agent. The Agent name is {0}. The exception is {1}
Problem This is an internal failure.
User response Contact IBM service.
HMGR1016E: An internal failure occured in an AgentClass. The AgentClass name is {0}. The exception is {1}
Problem This is an internal failure.
User response Contact IBM service.
HMGR1017I: An attempt to create a backup Agent has failed. The message could not be delivered to the target. The Agent is {0}.
Problem A communication problem was encountered. The message will be retried.
User response Ensure that all network paths are operating properly.
HMGR1018I: An attempt to cancel creation of a backup Agent has failed. The AgentClass does not have a request scheduled for Agent {0}.
Problem An internal inconsistency has been detected.
User response None. Informational only.
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}].
Problem A message was sent via the high availability manager Agent framework and received by this member. However, the channel name included in the message does not match any existing AgentClass or Agent channel name. It is possible for this to occur if the receiving component associated with the channel name in the message was destroyed while the message was in flight.
User response See the problem determination information on the WebSphere Application Server Support Web page, http://www.ibm.com/software/webservers/appserv/was/support, for help in determining the cause of this problem.
HMGR1106I: An out of specification group was found while processing the policy for group {0}. Too many members are active.
Problem While performing policy processing, it was discovered that more members of the group are active then should be.
User response No action is required. If problem continues, check previous messages for the original source of the problem.
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}.
Problem While performing policy processing, it was discovered that the group is not consistent with the policy and corrective actions were unable to make the group consistent with the policy at this time.
User response No action is required. If problem continues, check previous messages for the original source of the problem.
HMGR1108I: Unable to make group consistent with the specified policy. There are no available members to activate. The group name is {0}.
Problem While performing policy processing, it was discovered that the group is not consistent with the policy and corrective actions were unable to make the group consistent with the policy at this time.
User response This is probably a transient condition that will be resolved when current group members reach a stable state. If problem persists, check for problems with the component corresponding to the group name.
HMGR1109I: Unable to make group consistent with the specified policy. There are no available members to deactivate. The group name is {0}.
Problem While performing policy processing, it was discovered that the group is not consistent with the policy and corrective actions were unable to make the group consistent with the policy at this time.
User response This is probably a transient condition that will be resolved when current group members reach a stable state. If problem persists, check for problems with the component corresponding to the group name.
HMGR1200I: HA Manager administrative action requested. Operation is "{0}".
Problem An HA Manager administrative action was requested and has been logged for informational purposes only.
User response None. An informational message.
HMGR1201I: HA Manager administrative action requested. Operation is "{0}", the group is "{1}".
Problem An HA Manager administrative action was requested and has been logged for informational purposes only.
User response None. An informational message.
HMGR1202I: HA Manager administrative action requested. Operation is "{0}", the member is "{1}", the group is "{2}".
Problem An HA Manager administrative action was requested and has been logged for informational purposes only.
User response None. An informational message.
HMGR1203I: HA Manager administrative action requested. Operation is "{0}", current active member is "{1}", requested active member is "{2}", the group is "{3}".
Problem An HA Manager administrative action was requested and has been logged for informational purposes only.
User response None. An informational message.
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}".
Problem An asynchronous administrative operation was requested, and during background processing the specified group could not be found. Thus, no action was taken.
User response Retry the failing command with a valid GroupName parameter.
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}"
Problem An asynchronous administrative operation was requested, and during background processing the specified member could not be found. Thus, no action was taken.
User response Retry the failing command with valid Node Name and Server Name parameters.
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}".
Problem An asynchronous administrative operation was requested, and during background processing it was determined that the core group membership is changing. Thus, no action was taken.
User response Due to the timing of asynchronous operations, it is possible to encounter this situation. Wait for servers in this core group to enter a steady state (e.g. started or stopped) and retry the failing command.
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}".
Problem An asynchronous administrative operation was requested, and during background processing it was determined that the specified member or group is not in the correct state for the requested action. Thus, no action was taken.
User response Due to the timing of asynchronous operations, it is possible to encounter this situation. Verify the current state of the member or group. If necessary, retry the failing command.
HMGR2000I: An unusual event occurred while sending local state to the {0} manager. The exception is {1}.
Problem The intended partitioned-manager-group receiver member, may have already left the high-availability manager group.
User response None. An informational message.
HMGR2001E: An error occurred while sending local state to the {0} manager. The exception is {1}.
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.
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.
Problem A partitioned manager event handling method passed an unhandled exception to partitioned manager group. See the exception stack trace for more detail.
User response If you want this instance of partitioned manager group to be functional, recreate it.
HMGR2003E: Partitioned manager group received an inbound message which does not contain a valid header. The header is either absent or malformed.
Problem Partitioned manager group received an inbound state-distribution or application message with invalid header.
User response If the root cause cannot be determined and corrected, contact IBM Service.
HMGR2004E: Partitioned manager group received an inbound message associated with the {0} header. The header is not an existing manager set name.
Problem Partitioned manager group received an inbound state-distribution or application message associated with an unexpected header.
User response If the root cause cannot be determined and corrected, contact IBM Service.
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.
Problem The partitioned manager group event handler application has requested process termination.
User response None. An informational message.
HMGR3000E: A failure occured while adding server {0} on node {1} to core group {2}. The exception is {3}.
Problem See the exception stack trace for information as to why the action failed.
User response Correct the root cause of the problem and retry the operation. If the root cause cannot be determined, contact IBM Service.
HMGR3001E: A failure occured while removing server {0} on node {1} from core group {2}. The exception is {3}.
Problem See the exception stack trace for information as to why the action failed.
User response Correct the root cause of the problem and retry the operation. If the root cause cannot be determined, contact IBM Service.
HMGR3100I: The HA Manager work queue statistics detected a non-default value. The new base threshold is {0}.
Problem HA Manager detected that the JVM property ha.workqueue.threshold is configured for this process.
User response An informational message. No action required.
HMGR3101I: The work queue dump threshold changed to {0} for queue {1}. The data from threshold {2} is {3}.
Problem HA Manager detected that the work queue dump threshold changed.
User response An informational message. No action required.
HMGR5000E: An attempt to access configuration data has failed. The configuration data has not been initialized. The execution stack is {0}.
Problem An inconsistent internal state was detected. Processing cannot continue.
User response Contact IBM service.
HMGR5001E: An invalid configuration action has been attempted. The execution stack is {0}.
Problem An inconsistent internal state was detected. Processing cannot continue.
User response Contact IBM service.
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}.
Problem An internal inconsistency was detected. No recovery was possible.
User response Contact IBM Service
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}.
Problem An internal inconsistency was detected. No recovery was possible.
User response Contact IBM Service.
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}.
Problem An inconsistent internal state was detected. Processing should not continue.
User response Contact IBM service.
HMGR5005E: No active coordinators were found. The execution stack is {0}.
Problem An inconsistent internal state was detected. Processing should not continue.
User response Contact IBM service.
HMGR5006E: The DCS provider has not been initialized. The execution stack trace is {0}.
Problem A DCS operation was requested, but the DCS provider has not been initialized.
User response Contact IBM service.
HMGR5007E: An attempt to use the DCS provider to send a message has failed. The execution stack trace is {0}.
Problem A DCS operation was requested, but the caller has no identity.
User response Contact IBM service.
HMGR5008E: A bulletin board change notification has been received, but there is no data. The execution stack trace is {0}.
Problem A bulletin board operation failed.
User response Contact IBM service.
HMGR5009E: The host name for a process has changed. The execution stack trace is {0}.
Problem A configuration update operation failed.
User response Contact IBM service.
HMGR5010E: An attempt to reconstruct a streamed map has failed. The map has no entries. The execution stack trace is {0}.
Problem A streaming operation failed.
User response Contact IBM service.
HMGR5011E: An attempt to initialize the UserCallbacks service failed. The service is already initialized. The execution stack trace is {0}.
Problem An initialization operation failed.
User response Contact IBM service.
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}.
Problem An internal inconsistency was detected. No recovery was possible.
User response Contact IBM Service.
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}.
Problem An unexpected condition occurred.
User response Check the stack trace for a message that may help indicate the cause of the problem. If the problem cannot be solved, contact IBM Service.
HMGR5014E: An attempt to remove Bulletin Board posts for subject {0} failed. There are no posts for this subject.
Problem An inconsistent internal state has been detected.
User response Contact IBM Support.
HMGR5015E: An attempt to create a Server Power Controller failed. The class name is {0} and the exception is {1}.
Problem An unrecoverable error has been detected.
User response Contact IBM Support.
HMGR5016E: An attempt to inform the controller that the servant initialization completed has failed. The exception is {0}.
Problem An unrecoverable error has been detected.
User response Contact IBM Support.
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.hamanager.nls.HAManagerMessages.html

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