Explanation | The CollectiveRepository MBean successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The nodeName parameter specified is not valid. The nodeName cannot be null or an empty string. |
Action | Specify a valid nodeName parameter. |
Explanation | The memberId parameter specified is not valid. The memberId must be from a registerMember operation, and cannot be null or an empty string. |
Action | Specify a valid memberId parameter. |
Explanation | The Server Registration MBean has been successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The collective repository service is not available for processing requests. |
Action | Enable the collectiveController-1.0 feature and try again. |
Explanation | A server is uniquely specified by its server name, host name, and user directory. The server specified has already been registered. The server must not already exist in the repository. |
Action | Specify a server which has not already been registered. |
Explanation | The server specified does not exist in the repository. |
Action | Specify a server which exists in the repository. |
Explanation | The server name specified is not valid. The server name cannot be null or an empty string. |
Action | Specify a valid server name. |
Explanation | The host name specified is not valid. The host name cannot be null or an empty string. |
Action | Specify a valid host name. |
Explanation | The install directory specified is not valid. The install directory can not be null or an empty string. |
Action | Specify a valid install directory. |
Explanation | The user directory specified is not valid. The user directory can not be null or an empty string. |
Action | Specify a valid user directory. |
Explanation | The properties map cannot be null. |
Action | Specify a non-null properties map. |
Explanation | The property specified was not recognized. |
Action | Specify a supported property. |
Explanation | The value specified for a property is not valid. |
Action | Specify a valid value for the property. |
Explanation | The required userId property is missing, and must be specified. |
Action | Specify a value for the userId property. |
Explanation | Either the rpcUserPassword property or the sshPrivateKey property must be specified. |
Action | Specify a valid value for either the rpcUserPassword property or the sshPrivateKey property. |
Explanation | The sshPrivateKey and rpcUserPassword have both been specified. |
Action | Set either sshPrivateKey or rpcUserPassword, but not both. |
Explanation | A sshPrivateKeyPassword has been set without a corresponding sshPrivateKey. |
Action | Either remove the sshPrivateKeyPassword property or specify the corresponding sshPrivateKey. |
Explanation | The specified combination of the useSudo value and sudo options is not valid. |
Action | Either remove the other sudo options, or set the value of useSudo to true. |
Explanation | The host must be unique, and not registered already, or exist in the repository. |
Action | Specify a host which has not already been registered. |
Explanation | The specified host does not exist in the repository. |
Action | Specify a host which exists in the repository. |
Explanation | The CollectiveRepository MBean bootstrap operation could not be completed using the existing configuration information. The required bootstrap endpoint could not be determined. A configuration or other type of warning or error should have occurred. |
Action | A configuration or other type of warning or error has occurred. Check the previous warning or error messages for possible corrective action. |
Explanation | The specified internal error has occurred, and should be used to identify the source of the problem. |
Action | Use the information specified in the message to identify the likely source of the problem, and determine likely recommended solutions. |
Explanation | The keystore password specified is not valid. The keystore password can not be null nor an empty string. |
Action | Specify a valid keystore password. |
Explanation | A connection could not be established to the underlying repository server. |
Action | Verify the state and status of the collective controller services. |
Explanation | Access to the specified MBean operation is only available when accessed through IBM's JMX REST Connector. |
Action | Access this MBean through IBM's JMX REST Connector. |
Explanation | The CollectiveRepository MBean operation cannot be completed because required security services were unavailable to perform the authorization check. |
Action | Ensure server is configured properly and that the server was not shutting down or changing configuration at the time of the request. |
Explanation | A dump of content in the collective repository. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The dump operation could not locate the needed OSGi service to resolve symbols in the filename and would write to the server log instead. |
Action | No action is needed if a dump to the server log is acceptable. Otherwise, restart the server with the "clean" option and retry. |
Explanation | The dump operation could not access the specified file due to error and would write to the server log instead. |
Action | No action is needed if a dump to the server log is acceptable. Otherwise, check if the specified file can be accessed, resolve the issue and retry. |
Explanation | The ClusterManager MBean has been successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The ClusterManager MBean could not read the path from the collective repository. |
Action | Use the information provided by the cause to identify and resolve the problem. |
Explanation | The ClusterManager MBean could not create the path into the collective repository. |
Action | Use the information provided by the cause to identify and resolve the problem. |
Explanation | The ClusterManager MBean could not delete the path from the collective repository. |
Action | Use the information provided by the cause to identify and resolve the problem. |
Explanation | The ClusterManager MBean could not get the children of the path from the collective repository. |
Action | Use the information provided by the cause to identify and resolve the problem. |
Explanation | The required parameter cluster name is not valid or it is null. |
Action | Specify a valid cluster name to resolve the problem. |
Explanation | The ClusterManager MBean is not active, so it could not perform the requested operation. |
Action | Examine the error message and correct the problem. |
Explanation | This operation requires all members to be started. |
Action | Start all cluster members and try the operation again. |
Explanation | This operation requires at least 2 active cluster members. |
Action | Start all cluster members and try the operation again. |
Explanation | The specified cluster does not exist. |
Action | Examine the error message and correct the problem. |
Explanation | The jmxauth information is required for this operation. |
Action | Make sure collectiveMember feature is enabled in the server.xml file. The collectiveMember feature automatically publishes server's jmxauth information to collective controller server. |
Explanation | The jmxPort information is required for this operation. |
Action | Make sure the collectiveMember feature is enabled in the server.xml file and it is working properly. The collectiveMember feature automatically publishes server's jmxPort information to collective controller server. |
Explanation | The specified node exists in the collective repository but the data returned is null. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified directory could not be created. |
Action | Ensure the target directory exists and has the appropriate permissions. |
Explanation | The outbound SSL configuration from collective controller to collective member is not valid. |
Action | Make sure the SSL configuration in the server.xml file is correct. |
Explanation | Could not get the SSL factory from the outbound SSL configuration. |
Action | Make sure the SSL configuration in the server.xml file is correct. |
Explanation | The CollectivePlugin is unavailable and is required to complete this operation. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The CollectiveRegistration MBean operation cannot be completed because required security services were unavailable to perform the authorization check. |
Action | Ensure server is configured properly and that the server was not shutting down or changing configuration at the time of the request. |
Explanation | The ClusterManager MBean operation cannot be completed because required security services were unavailable to perform the authorization check. |
Action | Ensure server is configured properly and that the server was not shutting down or changing configuration at the time of the request. |
Explanation | The RepositoryConfiguration MBean has been successfully started and is available to process requests. |
Action | This message is for information purposes only. No action is needed. |