CHKW core group validation (6.x servers)

CHKW7200I: IBM WebSphere Validation.
Explanation No additional information is available.
Action Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.
CHKW7201I: CoreGroup Validation.
Explanation No additional information is available.
Action Use either the administration application or the command line scripting tool to update the part of the configuration that is in error.
CHKW7202E: The name of the core group stored in {0} is missing.
Explanation A valid core group name must be present in the document.
Action Provide a valid core group name.
CHKW7203E: The core group name {0} is not valid.
Explanation The core group name must follow WebSphere Application Server managed object naming conventions.
Action Provide a valid core group name.
CHKW7204E: The lower limit of the range of IP addresses for multicast in core group named {0} is missing.
Explanation There should be a lower limit for the range of IP addresses for multicast present in the document.
Action Provide a lower limit for the range of IP addresses for multicast. You can use "239.0.0.0" as the lower limit.
CHKW7205E: The upper limit of the range of IP addresses for multicast in core group named {0} is missing.
Explanation There should be an upper limit for the range of IP addresses for multicast present in the document.
Action Provide an upper limit for the range of IP addresses for multicast. You can use "239.255.255.255" as the upper limit.
CHKW7206E: The {0} transport type specified for core group named {1} is not valid.
Explanation Transport type must be "CHANNEL_FRAMEWORK", "UNICAST", or "MULITICAST".
Action Change your transport type to one of the supported transport types.
CHKW7207E: The "is-alive" timer value, {0}, measured in seconds, for the high-availability manager policy named {1}, is too low. The timer value must be at least {2}.
Explanation A high-availability manager policy must have a valid value for the "is-alive" timer.
Action Provide an appropriate valid value for the "is-alive" timer for the high-availability manager policy of concern.
CHKW7208E: The name of the policy factory for the {0} high-availability manager policy is missing.
Explanation A high-availability manager policy must have an appropriate policy factory.
Action Provide an appropriate policy factory name for the high-availability manager policy of concern.
CHKW7212E: The name of a high-availability manager policy associated with core group named {0} is missing.
Explanation All high-availability manager policies attached to a core group must have valid and unique names.
Action Provide a valid and unique name for the high-avalilabity policy of concern.
CHKW7213E: The high-availability manager policy name {0} associated with core group named {1} is not valid.
Explanation The high-availability manager policy name must follow WebSphere Application Server managed object naming conventions.
Action Provide a valid and unique name for the high-avalilabity policy of concern.
CHKW7214E: The name component of the match criteria having {0} as the value component, and associated with the high-availability manager policy named {1} is missing.
Explanation A match criteria object must have a valid name component.
Action Provide a valid name component for the match criteria of concern.
CHKW7215E: The name component of the match criteria having {0} as the value component, and associated with the high-availability manager policy named {1} is not valid.
Explanation The name component of a match criteria must follow the high-availability manager match criteria naming conventions.
Action Provide a valid name component for the match criteria of concern.
CHKW7216E: The value component of the match criteria having {0} as the name component, and associated with the {1} high-availability manager policy is missing.
Explanation A match criteria object must have a valid value component.
Action Provide a valid value component for the match criteria of concern.
CHKW7217E: The value component of the match criteria having {0} as the name component, and associated with the high-availability manager policy named {1} is not valid.
Explanation The value component of a match criteria must follow the high-availability manager match criteria naming conventions.
Action Provide a valid value component for the match criteria of concern.
CHKW7219E: The node name of a core group server having {0} as the server name is missing.
Explanation A core group server must have a valid node name.
Action Provide a valid node name for the core group server of concern.
CHKW7220E: The node name {0} of a core group server having {1} as the server name is not valid.
Explanation The node name must follow WebSphere Application Server managed object naming conventions.
Action Provide a valid node name for the core group server of concern.
CHKW7221E: The server name of a core group server having {0} as the node name is missing.
Explanation A core group server must have a valid server name.
Action Provide a valid server name for the core group server of concern.
CHKW7222E: The server name {0} of a core group server having {1} as the node name is not valid.
Explanation The server name must follow WebSphere Application Server managed object naming conventions.
Action Provide a valid server name for the core group server of concern.
CHKW7223I: No core group servers are associated with the core group {0}.
Explanation For a core group to be usable, it must not have an empty set of valid core group servers.
Action You might want to populate the core group server set of the core group with valid core group server entries.
CHKW7224I: No preferred coordinator servers are associated with core group {0}.
Explanation For coordinator execution in designated servers, there should not be an empty set of preferred coordinator servers attached to the core group.
Action If you want to execute coordinators in designated WebSphere servers, provide a populated set of valid preferred coordinator servers.
CHKW7225I: No high-availability manager policies are associated with the core group {0}.
Explanation For a core group to be usable, it must not be associated with an empty list of high-availability manager policies.
Action Provide a populated list of high-availability manager policies for the core group of concern.
CHKW7226I: No preferred servers are associated with the preferred server policy {0}.
Explanation For application execution in designated servers, there should not be an empty set of valid preferred servers.
Action If you want to execute applications associated with the preferred server policy in designated WebSphere servers, provide a populated set of valid preferred servers.
CHKW7227E: No servers are associated with the static policy {0}.
Explanation For application execution under static policy, there must not be an empty set of valid servers associated with the static policy.
Action Provide a populated set of servers for the static policy of concern.
CHKW7228I: No match criteria is associated with the high-availability manager policy {0}.
Explanation For a high-availability manager policy to be usable, there must not be an empty list of valid match criteria.
Action Provide a populated list of valid match criteria for the high-availability manager policy of concern.
CHKW7229I: No useful match criteria is associated with the high-availability manager policy {0}.
Explanation For a high-availability manager policy to be usable, there must not be an empty list of valid match criteria.
Action Provide a populated list of valid match criteria for the high-availibility manager policy of concern.
CHKW7230E: The high-availability manager policies {0} and {1} are considered the same. Both have the same set of match criteria.
Explanation Within the scope of a core group, high-availability manager policies must be associated with distinct sets of match criteria.
Action Make the high-availability manager policies unique by providing different sets of match criteria.
CHKW7231E: More than one high-availability manager policy having the same name {0}, is associated with the core group named {1}.
Explanation Within the scope of a core group, high-availability manager policies must have unique names.
Action Provide unique valid names for all the high-availability manager policies attached to the core group of concern.
CHKW7232E: More then one match criteria having the same name {0}, is associated with the high-availability manager policy named {1}.
Explanation Within the scope of a high-availability manager policy, the names of match criteria must be unique.
Action Provide unique valid names for the match criteria attached to the high-availability manager policy of concern.
CHKW7233E: More than one core group server associated with the core group named {2}, has the same node name {0}, and server name {1}.
Explanation The node name and server name combination of a core group server must be unique.
Action Provide unique node-qualified server names for all the core group servers.
CHKW7234E: More than one preferred coordinator server associated with the core group named {2}, has the same node name {0}, and server name {1}.
Explanation The preferred coordinator servers must be unique.
Action Provide unique preferred coordinator servers for the core group of concern.
CHKW7235E: More than one preferred server associated with the preferred server policy named {2}, has the same node name {0}, and server name {1}.
Explanation Within the scope of a preferred server policy, the preferred servers must be unique.
Action Provide unique preferred coordinator servers for the preferred server policy of concern.
CHKW7236E: More than one server associated with the static policy named {2}, has the same node name {0}, and server name {1}.
Explanation Within the scope of a static policy, all the servers attached to it must be unique.
Action Provide unique servers for the static policy of concern.
CHKW7237I: The value {0} specified for the number of coordinators for the core group named {1} is not within a supported range.
Explanation The value of the number of coordinators must be within the inclusive range of 1 and the number of core group servers.
Action Provide an appropriate value for the number of coordinators.
CHKW7238I: The value {0} specified for the number of active servers for the MOfN policy named {1} is not within a supported range.
Explanation The value of active servers must be within the inclusive range of 1 and the number of core group servers.
Action Provide an appropriate value for active servers.
CHKW7239E: The multicast port value {0}, specified for the core group named {1}, is too low. The value must be at least {2}.
Explanation The value of the multicast port must be a valid and avaliable port number.
Action Provide an appropriate value for multicast port.
CHKW7240E: The policy factory name {0} specified for the high-availability manager policy named {1} is not valid. The policy factory name must be {2}.
Explanation Each category of high-availability policy has a corresponding policy factory.
Action Provide the suggested policy factory name for the high-availability manager policy of concern.
CHKW7241E: The preferred coordinator server having node name {0}, and server name {1} that is associated with core group named {2}, is not a core group server.
Explanation The set of preferred coordinator servers must be a subset of core group servers.
Action Provide a preferred coordinator server which is also a core group server.
CHKW7242E: The preferred server with node name {0} and server name {1} that is associated with the preferred server policy named {2}, is not a core group server.
Explanation A set of preferred servers must be a subset of core group servers.
Action For the preferred server policy of concern, provide a preferred server which is also a core group server.
CHKW7243E: The server with node name {0}, and server name {1} that is associated with the static policy named {2}, is not a core group server.
Explanation The set of servers associated with a static policy must be a subset of core group servers.
Action For the static policy of concern, provide a server which is also a core group server.
CHKW7244E: The custom property name {0}, beneath {1}, is duplicated.
Explanation Within a list of custom properties, property names must be unique.
Action Provide unique custom property names.
CHKW7245E: The name of a custom property beneath {0} is missing.
Explanation A custom property must have a name.
Action Provide a name for the custom property.
CHKW7246E: The custom property name {0}, beneath a core group server is duplicated.
Explanation Within a list of custom properties, property names must be unique.
Action Provide unique custom property names for the core group server.
CHKW7247E: The name of a custom property beneath a core group server is missing.
Explanation A custom property must have a name.
Action For the core group server, provide a name for the custom property.
CHKW7248E: The name of the channnel-chain in core group named {0} is missing.
Explanation A channel-chain must have a name.
Action Provide an appropriate name for the channel-chain.
CHKW7271E: The core group server with node name {0} and server name {1} that is associated with core group named {2}, does not exist.
Explanation A specified core group server must exist in the WebSphere cell.
Action Provide an appropriate existing node-qualified WebSphere server as the core group server.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: May 16, 2012 5:08:07 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.websphere.validation.base.config.level60.coregroupvalidation_60.html

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