Explanation | The specified user does not have the appropriate authorization to access the specified management operation. |
Action | No action is required. |
Explanation | The specified entry is already defined for the specified role binding. Duplicate entries are not supported. |
Action | Remove the duplicate entry. |
Explanation | Notification clients are required to make requests within the allowed time to avoid timeouts. |
Action | Ensure the server is still accepting HTTP requests. |
Explanation | There is a limit on the number of concurrent clients that can sign up for notifications. |
Action | Ensure notification clients are authentic and required. Restarting the server will reset all notification clients. |
Explanation | The JMX REST connector is now ready to be accessed at the given service URL. |
Action | No action is required. |
Explanation | The notification client has the maximum number of concurrent MBean listener registrations allowed. |
Action | Ensure current MBean listener registrations are unique and required. Remove unnecessary MBean listener registrations or create a new notification client. |
Explanation | An attempt was made to access a path that is outside the configured read/write region. |
Action | Correct the path to indicate one that is within the configured read/write region. |
Explanation | This is an internal server error thrown because the specified service is not available. |
Action | Restart the server with the "clean" option. |
Explanation | The download request for the specified file has completed successfully. |
Action | This is an informational message, and no action is required. |
Explanation | The upload request for the specified file has completed successfully. |
Action | This is an informational message, and no action is required. |
Explanation | The delete request for the specified file has completed successfully. |
Action | This is an informational message, and no action is required. |
Explanation | The delete request for the specified file was unsuccessful, it may be in use by another process. |
Action | Verify that the file is not being used by another process and that appropriate permissions exist that allow the file to be deleted. |
Explanation | The specified path is not valid, and was not able to be located. |
Action | Ensure a valid path containing no invalid characters or values is specified. |
Explanation | There are no configured writable locations on the routing server. |
Action | Ensure that at least 1 writable location is configured on the routing server. |
Explanation | Expansion for the specified uploaded archive could not be completed. |
Action | Ensure the archive is not corrupt. |
Explanation | The necessary archive expander utility could not be located. |
Action | Ensure the Liberty installation directory is not corrupt. |
Explanation | The provided identifier does not match any tasks currently being held in the task registry. |
Action | Query a valid identifier that has not been recycled. |
Explanation | The post transfer action options must be null, empty or a comma-separated list with the same length as the actions list. |
Action | Ensure the post transfer action options contain a valid value. |
Explanation | The WebSphere Java Management Extensions REST client encountered an error while preparing a request for the server |
Action | Examine the server logs for further information. |
Explanation | The WebSphere Java Management Extensions REST client was unable to process a response from the server |
Action | Examine the server logs for further information. |
Explanation | The WebSphere Java Management Extensions REST client received an unexpected response code from the server |
Action | Examine the server logs for further information. |
Explanation | The server raised an exception handling the client request, but the client could not parse a Throwable object from the server error stream. The class of the Throwable object may not be available to the client. |
Action | Examine the server logs for further information. |
Explanation | The connection to the server or was closed or has failed. |
Action | Check that the REST connector feature is enabled on the server and obtain a new connection to the server. |
Explanation | The client may have out-of-date information or the REST connector feature on the server may have been disabled. |
Action | Check that the REST connector feature is enabled on the server and obtain a new connection to the server. |
Explanation | The class name argument must not be null. |
Action | Provide a non-null class name when calling the method. |
Explanation | The attribute name argument must not be null. |
Action | Provide a non-null attribute name when calling the method. |
Explanation | The argument containing an array of attribute names must not be null. |
Action | Provide a non-null array of attribute names when calling the method. |
Explanation | The Attribute argument must not be null. |
Action | Provide a non-null Attribute when calling the method. |
Explanation | The AttributeList argument must not be null. |
Action | Provide a non-null AttributeList when calling the method. |
Explanation | The ObjectName argument must not be null. |
Action | Provide a non-null ObjectName when calling the method. |
Explanation | The exception wraps a Throwable object returned from the server that is not normally expected for this operation. |
Action | Examine the server logs for further information. |
Explanation | The credentials provided when obtaining the connection were incorrect. The user may not exist or may not have authority to access the server, or the password may be incorrect. |
Action | Correct the user name or password, then obtain a new connection. |
Explanation | The ObjectName argument is a pattern but the method requires an ObjectName matching exactly one MBean. |
Action | Provide an ObjectName argument without wildcards that will match exactly one MBean. |
Explanation | The operation requires a registered MBean, but no MBean with the given ObjectName was registered. |
Action | Ensure the MBean is registered before attempting to perform management operations on it. |
Explanation | The MBean does not provide an attribute of the given name. |
Action | Obtain the MBean information to confirm which attributes the MBean provides. |
Explanation | The MBean does not provide an operation of the given name. |
Action | Obtain the MBean information to confirm which operations the MBean provides. |
Explanation | The NotificationListener was not added or has already been removed and is not currently registered to receive notifications from the given MBean. |
Action | Make sure the calling code tracks which NotificationListeners have been added and removed or catch and handle the exception. |
Explanation | A notification could not be delivered to one or more NotificationListeners because a registered NotificationListener was not found or there was an exception during delivery of the notification. |
Action | If the notification should have been delivered to a registered NotificationListener, check the logs for exceptions. |
Explanation | The server became unavailable and did not become available again within the configured maximum time allowable. |
Action | Check the network connection and ensure that the server is running with the REST connector feature enabled. |
Explanation | The server has become unavailable, but the client will attempt to restore the connection for the duration of the configured maximum time allowable. |
Action | If the server is intentionally restarting, no action is required. Otherwise, check the network connection and ensure that the server is running with the REST connector feature enabled. |
Explanation | The connection to the server was temporarily lost but has been restored successfully. Exceptions were encountered while adding NotificationListeners, so some notifications may not be received. |
Action | Check the exceptions included with the notification and re-register NotificationListeners after correcting the problems. |
Explanation | The connection to the server was temporarily lost but has been restored successfully. Any registered NotificationListeners will continue to receive notifications. |
Action | None |
Explanation | The value for the parameter 'serviceURL' cannot be null. |
Action | Re-connect to the JMX REST Connector using a non-null JMXServiceURL value. |
Explanation | The specified endpoint value is not valid. |
Action | Re-connect to the JMX REST Connector using a valid endpoint value that is of type String and has the format "host:port". |
Explanation | None of the specified endpoints were available during the JMX REST Connector's initialization. |
Action | Re-connect to the JMX REST Connector using at least 1 available endpoint. |
Explanation | The credentials provided are incorrect, expired, incomplete, or denied authorization. |
Action | Verify that the user credentials have correct authentication and authorization, then obtain a new connection. |
Explanation | The member connected to the controller. |
Action | No action required. |
Explanation | The member disconnected from the controller. |
Action | No action required. |
Explanation | The specified OSGi service is not available. |
Action | Restart the server with the "clean" option. |
Explanation | The specified node does not exist in the repository. |
Action | Ensure the specified host is registered with the collective. |
Explanation | The file system path was not specified in the appropriate file operation white list. |
Action | Ensure the specified file system path is in the appropriate file operation white list. |
Explanation | Archive expansion on the specified host could not be completed due to the specified error. |
Action | Ensure that the host was properly registered, including its java home and read/write lists. |
Explanation | The specified command did not complete within the timeout limit. |
Action | Ensure that the host is available and the command is valid for that host. |
Explanation | The specified command did not run as expected and returned an unexpected code. |
Action | Ensure that the command is valid for the host. |
Explanation | The specified archive did not contain a root directory matching wlp/bin. |
Action | Ensure that the specified file is a valid WebSphere Application Server Liberty Profile archive. |
Explanation | The product did not find the specified Java archive (JAR) within the controller wlp/lib directory. |
Action | Ensure that the controller wlp/lib directory is not corrupted. |
Explanation | The specified error stopped the post transfer action. |
Action | Correct the specified error and redeploy the archive. |
Explanation | The post transfer action must be one of the supported actions. |
Action | Correct the requested action to be one of the supported actions in the documentation. |
Explanation | The specified post transfer action has completed successfully. |
Action | This is an informational message, and no action is required. |
Explanation | The collective controller began uploading the specified file to the specified host location. |
Action | This is an informational message, and no action is required. |
Explanation | The collective controller successfully finished uploading the specified file to the specified host location. |
Action | This is an informational message, and no action is required. |
Explanation | The uploaded archive file is expanding into the specified host location. |
Action | This is an informational message, and no action is required. |
Explanation | The uploaded archive file successfully expanded into the specified host location. |
Action | This is an informational message, and no action is required. |
Explanation | The product is now deleting the uploaded archive file. |
Action | This is an informational message, and no action is required. |
Explanation | The product successfully deleted the uploaded archive file from the host. |
Action | This is an informational message, and no action is required. |
Explanation | The specified post transfer action is now running. |
Action | This is an informational message, and no action is required. |
Explanation | The collective controller cannot perform the actions because the collective controller configuration does not enable custom actions. |
Action | Set enableCustomActions to true in the configuration of the collective controller. |
Explanation | The specified node does not exist in the repository, probably because the host is not registered with the collective controller. |
Action | Ensure the specified host is registered with the collective controller. Run the collective registerHost command to do the registration. |
Explanation | The specified pre-transfer action is now running. |
Action | This is an informational message, and no action is required. |
Explanation | The collective controller began deleting the specified file. |
Action | This is an informational message, and no action is required. |
Explanation | The collective controller successfully finished deleting the specified file. |
Action | This is an informational message, and no action is required. |
Explanation | The specified error stopped the pre-transfer action. |
Action | Correct the specified error and retry the operation. |
Explanation | The specified pre-transfer action has completed successfully. |
Action | This is an informational message, and no action is required. |
Explanation | The referenced httpEndpoint could not be found. |
Action | Change the httpEndpointRef attribute to refer to an existing httpEndpoint element, or create a new httpEndpoint with the reference id. |
Explanation | The httpEndpoint element was configured with host="*", but a usable host name could not be found for any network interface. An HTTP endpoint requires a host value that can be resolved to an active network interface. |
Action | Specify a host name for the httpEndpoint element, or make sure a usable host name exists for one of the network interfaces. |
Explanation | The httpEndpoint element was configured with no httpPort and no httpsPort. |
Action | Configure either an httpPort, or an httpsPort, or both, for the httpEndpoint element. |
Explanation | The enable attribute was set to false for the httpEndpoint element. |
Action | Set enable="true" for the httpEndpoint element. |
Explanation | The specified httpOptions element is not available in the configuration. |
Action | Create the specified httpOptions element in the configuration. |
Explanation | An EndpointRoutingInfoMBean is created for each collective member. The MBean has information about HTTP endpoints of the member. |
Action | No user action is required. |
Explanation | An EndpointRoutingInfoMBean is created for each collective member. The MBean is deactivated when the server is stopped. |
Action | No user action is required. |
Explanation | An ApplicationRoutingInfoMBean is created for each application on a collective member. The MBean is registered when the application is started for the first time. |
Action | No user action is required. |
Explanation | An ApplicationRoutingInfoMBean is created for each application on a collective member. The MBean is unregistered when the application is removed from the collective member. |
Action | No user action is required. |
Explanation | The ApplicationRoutingInfoMBean for an application is updated when the routing information for an application is updated. |
Action | No user action is required. |
Explanation | An application did not start successfully. An ApplicationRoutingInfoMBean is not created until an application starts successfully. |
Action | Fix the problem that causes starting of the application to fail. |
Explanation | Routing information is created as artifacts become known to the collective controller. |
Action | No user action is required. |
Explanation | Routing information is removed when artifacts are removed from the collective configuration. |
Action | No user action is required. |
Explanation | Routing information is updated as artifacts change in the collective. |
Action | No user action is required. |
Explanation | Collective members publish ApplicationRoutingInfoMBean information to the collective controller. The information published was unusable. |
Action | Investigate errors in the collective member. |
Explanation | The RoutingInfoManager MBean successfully started and is available to process requests. |
Action | No user action is needed. |
Explanation | A dump of state of the RoutingInfoManger. |
Action | No user 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 | Relationships between artifacts are added as information becomes known to the collective controller. |
Action | No user action is required. |
Explanation | Relationships between artifacts are removed as information becomes known to the collective controller. |
Action | No user action is required. |
Explanation | mailSession was created successfully with the infomation provided in the server.xml |
Action | No action is necessary at this time |
Explanation | The default catalog loaded because no catalog has been created yet. |
Action | No action is required. |
Explanation | The SingletonMessenger MBean successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The catalog does not contain a tool with the specified tool ID. |
Action | No action is required. |
Explanation | The SingletonMessenger MBean successfully deactivated. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product cannot parse the Admin Center catalog content stored in the underlying persistence layer. The syntax of the data appears to be corrupt. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The server created a new singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The content stored in the underlying persistence layer for the Admin Center catalog does not match the expected type. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The server removed the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | A problem occurred while accessing the underlying persistence layer when loading the Admin Center catalog. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The messenger connection successfully connected to the target server. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The persisted Admin Center catalog is incomplete. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The Messenger connection successfully disconnected from the server. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The messenger disconnected from the server. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The Admin Center catalog loaded from persisted storage. |
Action | No action is required. |
Explanation | The catalog already contains a tool with the specified tool ID. |
Action | A tool with the same name and version already exists in the catalog. Specify an alternate tool name (or version) and try again. |
Explanation | The candidate is registered. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The tool object to add to the catalog failed one or more validation rules. The message contains information about the first rule that failed. |
Action | Take corrective action to resolve the specified rule and submit the request again. |
Explanation | The candidate is unregistered. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product cannot parse the file because the file contents do not use valid JSON syntax. |
Action | Restore the file from a backup. The file will be overwritten with a valid copy if any changes to the Admin Center are made. |
Explanation | The product cannot complete the SingletonServiceMessenger MBean operation because the SingletonAuthorizer is unavailable. It may be stopping or the server is shutting down. |
Action | Ensure the server is started and retry the operation. |
Explanation | The file contents contain valid JSON but the attempt to map the JSON object to the specified class failed. |
Action | Restore the file from a backup. The file will be overwritten with a valid copy if any changes to the Admin Center are made. |
Explanation | The product cannot access the file. |
Action | Check the file permissions, check that the file is not locked and verify that the underlying file system and hardware are working correctly. |
Explanation | The indicated service identity registered as a leader candidate in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product cannot store the latest changes to the Admin Center catalog. The product will try to store future Admin Center catalog changes. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The indicated service identity unregistered as a leader candidate in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product cannot store the latest changes to the Admin Center catalog. The product will try to store future Admin Center catalog changes. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The indicated service identity registered as a leader candidate in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product removed the tool in persisted storage from the catalog because the tool data is not valid or incomplete. |
Action | Restore the catalog from a backup. The catalog file is overwritten with a valid copy if any changes to the Admin Center are made. |
Explanation | The product cannot access the file. |
Action | Check the file permissions, check that the file is not locked and verify that the underlying file system and hardware are working correctly. |
Explanation | The indicated service identity unregistered as a leader candidate in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product initialized the Admin Center persistence layer. |
Action | No action is required. |
Explanation | The indicated service identity registered as a participant in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The server attempted to identify the display name of the user, but the attempt failed. |
Action | Ensure that the specified user exists. If so, check trace and ffdc messages for possible corrective action. |
Explanation | The indicated service identity unregistered as a participant in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The operation requires that request parameter "url" be a URL. |
Action | Resubmit the request with a valid URL. |
Explanation | The indicated service identity registered as a participant in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The provided URL parameter is not a valid URL. |
Action | Resubmit the request with a valid URL. |
Explanation | The indicated service identity unregistered as a participant in the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The operation has no payload contents. The operation requires a payload of valid JSON syntax of the appropriate type. |
Action | Resubmit the request with a payload that uses valid JSON syntax of the appropriate type. |
Explanation | The indicated service identity is elected leader of the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The operation payload contents do not use valid JSON syntax. |
Action | Resubmit the request with a payload that uses valid JSON syntax of the appropriate type. |
Explanation | The indicated local service identity is no longer the leader of the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product does not interpret the operation payload contents as having the required type. |
Action | Resubmit the request with a payload that uses valid JSON syntax of the appropriate type. |
Explanation | The indicated remote service identity is elected leader of the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The toolbox for the specified user does not contain the requested tool. |
Action | No action is required. |
Explanation | The indicated service identity is no longer the leader of the singleton service. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The product restored the in-memory catalog and the persisted state to the default settings. |
Action | No action is required. |
Explanation | The catalog supports a reset operation using the HTTP DELETE method. To ensure catalogs are deleted only when intended, also specify a confirmation request parameter. |
Action | No action is required. |
Explanation | The toolbox already contains a tool with the specified tool ID. |
Action | A tool with the same name and version already exists in the toolbox. Specify an alternate tool name (or version) and try again. |
Explanation | The tool object to add to the toolbox failed one or more validation rules. The message contains information about the first rule that failed. |
Action | Take corrective action to resolve the specified rule and submit the request again. |
Explanation | The product restored the in-memory toolbox and the persisted state to the default settings. |
Action | No action is required. |
Explanation | The toolbox supports a reset operation using the HTTP DELETE method. To ensure toolboxes are deleted only when intended, also specify a confirmation request parameter. |
Action | No action is required. |
Explanation | The default toolbox loaded because the specified user does not have a toolbox yet. |
Action | No action is required. |
Explanation | The product cannot parse the Admin Center toolbox content stored in the underlying persistence layer. The syntax of the data appears to be corrupt. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The content stored in the underlying persistence layer for the Admin Center toolbox does not match the expected type. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | A problem occurred while accessing the underlying persistence layer when loading the Admin Center toolbox. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The persisted Admin Center toolbox is incomplete. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The Admin Center toolbox for the specified user loaded from persisted storage. |
Action | No action is required. |
Explanation | The product removed the tool in persisted storage from the toolbox because the tool data is not valid or incomplete. |
Action | Restore the toolbox from a backup. The toolbox file is overwritten with a valid copy if the user changes the toolbox. |
Explanation | The product cannot store the latest changes to the Admin Center toolbox. The product will try to store future Admin Center toolbox changes. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The product removed the tool in persisted storage from the toolbox because the tool is no longer available in the catalog. |
Action | The tool was removed from the toolbox because it is no longer available in the catalog. To restore the tool, install the tool back into the catalog. |
Explanation | The product loaded the Admin Center catalog from the previous persistence layer and stored a copy into the new persistence layer. The copy in the new persistence layer will be loaded by subsequent access to persisted storage. |
Action | No action is required. |
Explanation | The product loaded the Admin Center toolbox from the previous persistence layer and stored a copy into the new persistence layer. The copy in the new persistence layer will be loaded by subsequent access to persisted storage. |
Action | No action is required. |
Explanation | The product cannot parse the JSON payload because it exceeds the maximum allowable size for the operation. |
Action | Reduce the size of the JSON payload. |
Explanation | The catalog does not contain a tool with the specified tool ID and type. |
Action | No action is required. |
Explanation | The product uninstalled the tool feature and removed the tool from the catalog. |
Action | No action is required. |
Explanation | The list of tools to update does not match the list of tools from the current toolbox. |
Action | Fix the list of toolbox tools and submit the request again. |
Explanation | The list of tools to update already contains a tool with the specified tool ID. |
Action | A tool with the same name and version already exists in the list. Specify a unique tool name (or version) and try again. |
Explanation | The toolbox does not contain a tool with the specified tool ID and type. |
Action | Add the tool or fix the tool ID and type and then submit the request again. |
Explanation | The product stored the in-memory toolbox and the persisted state to the new settings. |
Action | No action is required. |
Explanation | The error prevented login password validation. |
Action | Check the log for details. Fix the problem mentioned in the error and try again. |
Explanation | The tool data for the specified user and tool loaded from persisted storage. |
Action | No action is required. |
Explanation | The content stored in the underlying persistence layer for the tool does not match the expected type. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The product cannot parse the tool data content stored in the underlying persistence layer. The syntax of the data might be corrupt. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | A problem occurred while accessing the underlying persistence layer when loading the tool data. This is an unrecoverable error. |
Action | See earlier log messages for possible corrective actions. |
Explanation | Tool data is successfully posted to the storage. |
Action | No action required. |
Explanation | The tool id is not in a format that the product can parse. |
Action | Contact the tool provider for possible corrective actions. |
Explanation | The product cannot read the payload because it exceeds the maximum allowable size for the operation. |
Action | Reduce the size of the payload. |
Explanation | The product cannot read the payload because it is empty. |
Action | Add payload to the request. |
Explanation | Tool data was successfully deleted from the persistence layer. |
Action | No user action required. |
Explanation | The file containing the tool data is locked by another process, causing an error when the product tries to delete tool data from the persistence layer. |
Action | Stop other programs from using the tool data file and then repeat the delete request. If this does not solve the problem, see log messages for possible corrective actions. |
Explanation | The specified folder cannot be deleted. |
Action | If the folder is in use by other programs, stop the programs from using the folder and then repeat the delete request. |
Explanation | The tool data for the specified user and tool was deleted from persisted storage. |
Action | No action is required. |
Explanation | A problem occurred while accessing the underlying persistence layer when deleting the tool data. |
Action | See earlier log messages for possible corrective actions. |
Explanation | A problem occurred while accessing the underlying persistence layer when storing the tool data. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The tool data from the persisted storage was modified after the client's last GET call. |
Action | Request a GET call to get the lastes version of tool data then perform the PUT operation. |
Explanation | A JSON marshalling error prevented the product from accessing the underlying persistence layer when storing the tool data. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The product initialized the Admin Center persistence layer for tool data loader. |
Action | No action is required. |
Explanation | A problem occurred while accessing the underlying persistence layer when promote the tool data from FILE persistence to COLLECTIVE persistence. |
Action | See earlier log messages for possible corrective actions. |
Explanation | An SSLSocketFactory implementation class was not found. |
Action | Get a JVM that supports Liberty profile products and SSL from Installation Manager offerings or developerWorks. Alternatively, check the ssl.SocketFactory.provider property in the JVM java.security file. |
Explanation | This internal server error occurred because the specified service is not available. |
Action | Restart the server with the clean option. |
Explanation | A problem occurred while accessing the underlying persistence layer when promoting the tool data from FILE persistence to COLLECTIVE persistence. |
Action | See earlier log messages for possible corrective actions. |
Explanation | The product cannot access the collective repository. |
Action | Ensure the collective controller is running and active. Ensure the connection to the collective controller is active. This error can occur if the collective controller is in the process of stopping. |
Explanation | The product cannot parse the data stored in the repository because the contents do not use valid JSON syntax. |
Action | Restore the repository contents from a backup. The repository contents are overwritten with a valid copy if any changes to the Admin Center are made. |
Explanation | The repository contents contain valid JSON syntax but the attempt to map the JSON object to the specified class failed. |
Action | Restore the repository contents from a backup. The repository contents are overwritten with a valid copy if any changes to the Admin Center are made. |
Explanation | The product encountered an error while accessing the collective repository. |
Action | Ensure the connection to the collective controller is functioning correctly. Ensure no errors prevent the collective controller from responding to repository access. |
Explanation | The product encountered an error while accessing the collective repository. |
Action | Ensure the connection to the collective controller is functioning correctly. Ensure no errors prevent the collective controller from responding to repository access. |
Explanation | This internal server error is thrown because the specified service is not available. |
Action | Restart the server with the clean option. |
Explanation | The product has entered an inconsistent state for the Collective REST API cache. The product will recover. Complete details of the condition which caused the inconsistent state is logged as FFDC. |
Action | No immediate action is required. If this message is occurring frequently, contact IBM support. |
Explanation | The specified service is not available. This is an internal server error. |
Action | Restart the server with the "--clean" option. |
Explanation | When invoking the CollectiveFileService REST endpoint, there must be a routing context set in the HTTP headers or in the HTTP query parameters. |
Action | Set the appropriate routing context and retry the invocation. |
Explanation | When invoking the CollectiveSchemaGenerator REST endpoint, a registered write list for the target host must exist. |
Action | Set up a write list for the registered host by updating its collective registration. |
Explanation | The remote file location must be within the registered white list of the target server. |
Action | Update the white list of the target server and retry the operation. |
Explanation | The given server identification must match a registered collective member in the collective repository. |
Action | Correct the server identification and retry the operation. |
Explanation | The given runtime identification must match a registered runtime in the collective repository. |
Action | Correct the runtime identification and retry the operation. |
Explanation | During startup the collective controller restored its state from the disk. Some files were corrupt but the collective controller recovered and corrected the problem. |
Action | No immediate action is required. Corrupted files may indicate a bad storage device. Check the storage device is healthy. |
Explanation | The collective controller is unable to connect or communicate with the specified replica. The specified replica may be down or there may be network connection issues. |
Action | Ensure that replica host and port for the specified replica in the <collectiveController> replicaSet configuration is correct, that the corresponding replica is running and that there are no network communication problems. |
Explanation | The collective controller is unable to delete a file from the file system. |
Action | Verify the permissions of the mentioned file, ensure the collective controller has delete permissions, and that the file is not locked. Ensure the storage device is functioning properly. |
Explanation | During normal work the collective controller writes its state to the disk in a dedicated directory. It is unable to create this directory. |
Action | Verify the permissions of the mentioned directory, and ensure the collective controller has write/modify permissions. Check that the storage device has enough free disk space. Ensure the storage device is functioning properly. |
Explanation | During startup the collective controller tries to restore its state from the disk. It encountered files that indicate a version which is not supported. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | During normal work, the collective controller writes its state to the disk in a dedicated directory. The value provided is not a directory. |
Action | Fix the value of the configuration parameter to identify a directory. |
Explanation | Communication among collective controller replicas is inconsistent. This might be a transient state due to a heavy load on the network or hosts. |
Action | Verify that hosts running collective controller are stable and have enough CPU power. Also, use the ping utility to measure round trip time (RTT) between hosts. High variations in RTT indicate that the system has a heavy load and it lacks network or CPU power resources. |
Explanation | The collective controller received a message that it cannot understand. The likely cause is a version mismatch between collective controller replicas. |
Action | Ensure the collective controller replicas have compatible versions. |
Explanation | The collective controller was unable to replicate the state to a majority of the replicas. A likely cause is network problems or unavailable replicas. |
Action | Ensure a majority of the replicas are running. Ensure the network connection connecting the replicas is functioning properly. |
Explanation | The collective controller opened a connection to the specified replica. This information denotes a healthy state. |
Action | No user action is required. |
Explanation | The collective controller closed the connection to a replica successfully. This is usually due to a planned replica set change or an orderly stopping of a replica. |
Action | No user action is required. |
Explanation | The collective controller is ready to accept requests. Consistency, high availability and load balancing are available. This message occurs after initialization ends, or when the replica set changes, either due to administrator actions or due to replica failure. |
Action | No user action is required. |
Explanation | The collective controller is temporarily unable to accept requests, but will probably be ready within a few seconds. This message occurs after initialization ends, or when the replica set changes, either due to administrator actions or due to replica failure. The system will automatically adjust to the new replica set. If there are not enough replicas to regain consistency and high availability, a separate message is written to the log with a higher severity. |
Action | No user action is required. |
Explanation | This is a periodic state report. Use this report to resolve future problems, if they occur. |
Action | No user action is required. |
Explanation | This collective controller replica synchronized with the other replicas. This replica was out of sync with the other replicas. This usually happens when the replica is started and joins an active repository, but can also happen when a replica is restarted or is disconnected from the other replicas for a period of time. |
Action | No user action is required. |
Explanation | The administrator requested to change the set of replicas in the collective controller. The change request is processing. |
Action | No user action is required. |
Explanation | Changing the active collective controller replica set was successful. The new set now can serve high availability and consistency. Replicas not in the current set can be shut down. |
Action | No user action is required. |
Explanation | During startup, the collective controller tries to restore its state from the disk. It checks for relevant files in the specified directory. |
Action | Verify the permissions. |
Explanation | The collective controller is unable to read data from the specified file. The problem might be a permissions issue or a storage device error. |
Action | Verify the permissions of the mentioned file, and ensure the collective controller has write permissions. Ensure the storage device is functioning properly. |
Explanation | The collective controller is unable to write data into the specified file. The problem might be a permissions issue, out of disk space error, or a storage device malfunction. |
Action | Check that the storage device has enough free disk space. Verify the permissions of the mentioned file, and ensure the collective controller has write permissions. Ensure the storage device is functioning properly. |
Explanation | An unexpected internal problem encountered, and the replica had to shutdown. |
Action | Restart the replica. If the problem persists, use the error details and see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The collective controller allows changes in the set of replicas if at least one replica is included in both the new set and the old set. |
Action | To completely change the set of replicas, use a staged approach, where every stage includes at least one replica in both the set before and after reconfiguration. For example, when moving from {A,B,C} to {D,E,F}, where each of A, B, C, D, E, F represents a collective controller replica, try {A,B,C} to {A,D,E,F} and then {A,D,E,F} to {D,E,F}. Or try {A,B,C} to {C,D,E} and then {C,D,E} to {D,E,F}. |
Explanation | The collective controller given configuration parameter must be a list of host:port, separated by spaces; for example, "10.0.0.11:10010 10.0.0.21:10010 10.0.0.31:10010". The provided value does not match this pattern. This can also indicate a failure in host translation, probably due to an error in the host name or address. |
Action | Fix the value of the configuration parameter. Ensure that it fits the required pattern and has the correct host names and ports. |
Explanation | The collective controller configuration parameter stated in the message must be the host name or IP address. The value that was provided is not in the correct format for a host name or IP address. |
Action | Fix the value of the configuration parameter. Ensure that it fits the required pattern and has the correct host name or IP address. |
Explanation | The collective controller configuration parameter mentioned in the message must be a boolean value (true or false). The value that was provided is not boolean. |
Action | Set the value of the configuration parameter to either true or false. |
Explanation | The collective controller configuration parameter specified is missing. |
Action | Check whether the default value fits your needs. If not, add the missing configuration parameter. |
Explanation | The collective controller configuration parameter specified is missing. The collective repository is unable to start. |
Action | Add the missing collective controller configuration parameter. |
Explanation | The socket bind operation did not succeed. A common cause is that the port number is already in use. A second cause is the host configured does not match the system configuration. |
Action | Check that the collective controller is configured to use an available port number. Make sure the host matches the system configuration. |
Explanation | The collective controller configuration parameter stated in the message must be a valid port. The value that was provided is not an integer. |
Action | Fix the value of the configuration parameter and ensure the port value is an integer. |
Explanation | The collective controller configuration parameter stated in the message must be an integer in the given range. The value that was provided is not an integer in the correct range. |
Action | Fix the value of the configuration parameter and ensure it fits the above pattern. |
Explanation | The collective controller configuration parameter stated in the message must be a string, delimited using double quotes. The value was not identified as a string. |
Action | Fix the value of the configuration parameter to be a double quoted string. |
Explanation | The collective controller configuration parameter stated in the message must be one of a list of predefined values. The value provided is not one of these values. |
Action | Fix the value of the configuration parameter and ensure it is a predefined value. |
Explanation | A replica can either be part of an initial replica set, or join an already running replica set, and replicate the existing data from the replicas that were already running. The collective controller identified that none of the running replicas were previously part of a running collective controller replica set, and an initial set was not defined. |
Action | Fix configuration to define an initial set of replicas. |
Explanation | The collective controller requires that most replicas be active and reachable. Changing the replica set stops the collective controller and it will not be able to replicate properly. |
Action | Ensure that the replicas are active and available. You may need to verify that the network is functioning properly. |
Explanation | The mentioned replica's configuration states that it is part of a different replica set, and should not connect to this replica set. |
Action | Fix the configuration of the mentioned replica so that the replica set value will not contain replicas from a different replica set, or change the mentioned configuration parameter to be the same as in this replica set. |
Explanation | You can modify these properties only when this replica is the only replica in the set or when it is a standby replica. |
Action | You need to remove this replica from the replica set (making it to a standby replica), update the properties in server.xml and then add it back to the replica set. |
Explanation | These properties cannot be modified after the initial start of the collective controller. |
Action | Restore the initial values of these properties in server.xml, so that the controller will function properly after the next restart. |
Explanation | The server configuration updates were successful. |
Action | No user action is required. |
Explanation | The collective controller instances discovered an inconsistent configuration. |
Action | See the WebSphere Application Server information center for help configuring a collective controller. |
Explanation | The collective controller can only add a new replica to the replica set if it is connected to another replica in the replica set. |
Action | Ensure the configuration of the replica set is correct in the new replica's server.xml and start it, before adding it to the replica set. |
Explanation | These properties cannot be modified once the collective controller replica set containing this replica, has more than one replica. |
Action | Remove this replica from the replica set, update the properties, and then add it to the replica set. |
Explanation | During startup the collective controller tries to restore its state from the disk. The encountered state indicates that the collective controller uses an unsupported version. |
Action | See the problem determination information on the WebSphere Application Server Support Web page at http://www.ibm.com/software/webservers/appserv/was/support in the Upgrade/Downgrade section. |
Explanation | The collective controller can only add a new replica to the replica set if it is able to run the version currently used by the replica set. |
Action | Ensure that the new replica uses a version that the replica set supports. |
Explanation | The collective controller requires that replica storage not be destroyed. If a replica loses its data, the only way to add data back to the new replica is to remove the previous instance from the replica set. After the replica was removed you can add it to the replica set again and the collective controller will restore the data. |
Action | Remove and then add the replica to the replica set using corresponding scripts. |
Explanation | It is likely that there was an incomplete upgrade or downgrade process and thus there are replicas that run in different versions. This state may lead to a split brain and thus the replicas that run in a lower version terminate to avoid this. |
Action | If this happens during an upgrade process then upgrade this replica. If this happens during a downgrade process, then perform a downgrade to the remote replica. See the problem determination information on the WebSphere Application Server Support Web page at http://www.ibm.com/software/webservers/appserv/was/support in the Upgrade/Downgrade section. |
Explanation | Before the upgrade process completes, replicas have different versions. The upgrade process is still running. |
Action | Finish upgrading all replicas and then start them. |
Explanation | The collective controller determined that all replicas in the current active replica set are able to run a newer version of their protocol. |
Action | No user action is required. |
Explanation | Upgrading the active collective controller replica protocol was successful. |
Action | No user action is required. |
Explanation | The collective controller discovered that the connectivity graph of the replicas is not transient. |
Action | Ensure that there are no network communication problems. |
Explanation | The collective controller experiences periodic connectivity problems. |
Action | Ensure that both replicas are running, stable, and have a good connection between them. |
Explanation | The collective controller connectivity problems are similar to those caused by a firewall. |
Action | Ensure that there is no firewall blocking connections between replicas. |
Explanation | Time to write repository data to disk exceeds a threshold. |
Action | If repository errors occur, check disk I/O performance. |
Explanation | The ServerCommands MBean has been successfully started and is available to process requests. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A general internal error occurred. |
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 time to execute the command exceeded the timeout value. This might be caused by a busy network or the host machine was slow. |
Action | Tune up the network and the target machine or specify a longer timeout value in the server configuration. |
Explanation | Liberty profile installation is not found at the specified directory. |
Action | Check the Liberty profile installation directory and retry the operation. |
Explanation | An error occurred while connecting to the specified host. |
Action | Check the specified host and make sure that the credentials are correct. |
Explanation | An error occurred while connecting to the specified host. |
Action | Check the specified host and make sure that the credentials are correct. |
Explanation | sudo is not supported on the specified host. |
Action | Do not specify useSudo, sudoUsername, or sudoPassword when connecting to this host. |
Explanation | sudo is not supported with ssh public and private key authentication. |
Action | Do not specify useSudo, sudoUsername, or sudoPassword when using ssh key authentication. |
Explanation | An error occurred while matching the pattern. |
Action | Rerun the command. |
Explanation | The controller failed to run the command on the target host due to an error. |
Action | Review the error message, correct the error, and run the command manually on the target host. |
Explanation | The input parameters are mandatory. |
Action | Rerun the command with all mandatory parameters. |
Explanation | Unable to create new directories in the specified location. |
Action | Check the permissions of the specified directory and give appropriate read and write permissions. |
Explanation | Unable to create files in the specified location. |
Action | Check the permissions of the specified directory and give appropriate read and write permissions. |
Explanation | An error occurred while setting the environment on the target host. |
Action | Check the operating system shell on the target host. |
Explanation | There was a problem when deleting the specified directory on the specified remote host. |
Action | Check to ensure that the remote host is accessible and that the directory is writable. |
Explanation | An error occurred while opening the specified log file. |
Action | Check the error messages. Fix the errors and re-run job. |
Explanation | An error occurred while setting desired permissions on the specified file. |
Action | Check the user permissions and rerun the operation. |
Explanation | The specified location is not a directory on the remote host. |
Action | Check the specified location and make sure that this is a directory instead of a file on the remote host. |
Explanation | An error occurred while creating the specified directory on the remote host. |
Action | Check the parent file permissions and make sure that it is writeable. |
Explanation | The specified file does not exist. |
Action | Ensure that the file exists. |
Explanation | The specified directory is not a valid directory. If it does not exist, the creation of this directory failed. |
Action | Ensure that the specified directory is not a file and that the server has permission to create it if it does not exist. |
Explanation | The specified file does not exist on the remote host. |
Action | Check to ensure that the file exists in the specified directory on the remote host. |
Explanation | An error occurred while reading the repository in the collective controller. |
Action | Correct the error condition and try again. |
Explanation | The ServerCommands MBean operation cannot be completed because required security services were unavailable to perform the authorization check. |
Action | This can occur if the server is shutting down or changing configuration at the time of the request. |
Explanation | A request to place a host into maintenance mode is being processed. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A request to place a server into maintenance mode is being processed. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A request to place a host or server into maintenance mode is being sent to another controller for processing. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A host has been placed into maintenance mode. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A server has been placed into maintenance mode. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A request to take a host out of maintenance mode is being processed. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A request to take a server out of maintenance mode is being processed. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A host has been taken out of maintenance mode. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A server has been taken out of maintenance mode. |
Action | This message is for information purposes only. No user action is required. |
Explanation | A request to change the maintenance mode of a host could not be processed because the host name is not recognized. |
Action | Check that the host name was specificed correctly. |
Explanation | A request to change the maintenance mode of a server could not be processed because the host name, user directory, or server name is not recognized. |
Action | Check that the host name, user directory, and server name are specified correctly. |
Explanation | A request to place a server into maintenance mode failed because the scaling controller cannot find an alternate server to replace it. |
Action | Consider re-issuing the request using the option to force the request even if it causes a violation of autoScaling policy. |
Explanation | The MaintenanceModeMBean operation cannot be completed because required security services were unavailable to perform the authorization check. |
Action | This can occur if the server is shutting down or changing configuration at the time of the request. |
Explanation | The collective controller is stopping and cannot perform a requested maintenance mode function. |
Action | Retry the request on another active collective controller. |
Explanation | The server is configured to use host credentials but authentication credentials are not set for the target host computer. |
Action | Disable useHostCredentials for the server or run the updateHost command to set valid credentials for the host. |
Explanation | The collective controller maintains the last 100 deployment results with old deployments being removed in favor of new ones. |
Action | This message is for information purposes only. No user action is required. |
Explanation | The DeployService has been successfully started and is available to process requests. |
Action | This message is for information purposes only. No user action is required. |
Explanation | The DeployService will only deploy to a host one time in each deployment request. To deploy again to the same host, another deployment request must be created. |
Action | Create an additional deployment request each time the same host is to receive a deployment. |
Explanation | An error prevented the writing of a deploy command to the repository. You might need to manually start and stop collective members deployed with these commands. |
Action | Remove the affected member from the collective, stop the member server, delete it from its host, and try the deploy again. |
Explanation | The ClusterMember MBean successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | An unexpected error occurred while the MBean was creating the node in the collective controller repository. |
Action | Examine the exception and correct the problem. |
Explanation | An unexpected error occurred while the MBean was deleting the node in the collective controller repository. |
Action | Examine the exception and correct the problem. |
Explanation | An unexpected error occurred while the MBean was reading the node in the collective controller repository. |
Action | Examine the exception and correct the problem. |
Explanation | An SSL context could not be created with the server's SSL certificate. |
Action | Check the server's SSL configuration and re-register the server to the collective controller. |
Explanation | The JMX authentication information is required to make a JMX connection to the specified target server. |
Action | Check if the target server is successfully bootstrapped to the collective controller. |
Explanation | The host name property of the JMX authentication information is required to make a JMX connection to the specified target server. |
Action | Check if the target server is successfully bootstrapped to the collective controller. |
Explanation | The port number of the JMX authentication information is required to make a JMX connection to the specified target server. |
Action | Check if the target server is successfully bootstrapped to the collective controller. |
Explanation | The required keystore for JMX routing is not configured. |
Action | Ensure the keystore is specified in the server.xml file. |
Explanation | The required collective controller repository reader is not started. |
Action | Check server configuration to make sure required features for JMX routing are present. |
Explanation | An attempt was made to access a path that is outside the configured read/write region. |
Action | Ensure the requested path is within configured read/write region. |
Explanation | The specified file system path cannot be resolved. |
Action | Provide a valid file system path. |
Explanation | An attempt was made to read information from a path that is outside the configured read region. |
Action | This message is for information purposes only. No action is needed. |
Explanation | An attempt was made to write information to a path that is outside the configured write region. |
Action | This message is for information purposes only. No action is needed. |
Explanation | The archive was successfully created. |
Action | This message is for information purposes only. No action is needed. |
Explanation | The archive creation request failed. |
Action | This message is for information purposes only. No action is needed. |
Explanation | An attempt was made to read information from a path that is outside the configured read region. |
Action | This message is for information purposes only. No action is needed. |
Explanation | An attempt was made to write information to a path that is outside the configured write region. |
Action | This message is for information purposes only. No action is needed. |
Explanation | The archive was successfully expanded. |
Action | This message is for information purposes only. No action is needed. |
Explanation | The archive expand request failed. |
Action | This message is for information purposes only. No action is needed. |
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 | You have received this internal server error because the specified service is not available. |
Action | Restart the server with the "clean" option. |
Explanation | The specified attribute from FileServiceMXBean was updated successfully. |
Action | No action is required. |
Explanation | A new file transfer client has connected with the specified connection identifier. |
Action | This is an informational message, and no action is required. |
Explanation | The client-side of the JMX REST connector encountered an error, and the specified message was generated. |
Action | Use the generated error message to identify, and correct the issue that caused this error, and rerun the operation. |
Explanation | The server-side of the JMX REST connector encountered an error, and generated the specified message. |
Action | Use the generated error message to identify, and correct the issue that caused this error, and rerun the operation. |
Explanation | The credentials provided when obtaining the connection are incorrect. The user may not exist, may not have authority to access the server, or the password may be incorrect. |
Action | Correct the user name or password, then obtain a new connection. |
Explanation | The file transfer client received an unexpected response code from the server. |
Action | Use the client response code to identify, and resolve the cause of this issue, and rerun the operation. |
Explanation | The download request of the specified file was successful. |
Action | This is an informational message, and no action is required. |
Explanation | The specified operation is not supported by the file transfer client. |
Action | Request an operation that is supported by the file transfer client. |
Explanation | The upload request of the specified file was successful. |
Action | This is an informational message, and no action is required. |
Explanation | The delete request of the specified file was successful. |
Action | This is an informational message, and no action is required. |
Explanation | The delete request of the specified collection was successful. |
Action | This is an informational message, and no action is required. |
Explanation | The collective features provide the implementation for the RepositoryClient, and no such implementation could be found. |
Action | Specify a collective feature such as collectiveMember-1.0 or collectiveController-1.0 and define any required configuration to resolve this issue. |
Explanation | The RepositoryConnectionFactory requires a specific RepositoryClientDelegate implementation, and an additional implementation has been registered as an OSGi service. Only one implementation is allowed. |
Action | Remove any third party or custom features which include this specified bundle. |
Explanation | The collective features provide the implementation for the RepositoryMember, and no such implementation could be found. |
Action | Specify a collective feature such as collectiveMember-1.0 or collectiveController-1.0 and define any required configuration to resolve this issue. |
Explanation | The RepositoryConnectionFactory requires a specific RepositoryMemberDelegate implementation, and an additional implementation has been registered as an OSGi service. Only one implementation is allowed. |
Action | Remove any third party or custom features which include this specified bundle. |
Explanation | The <collectiveMember> element is missing values for required configuration attributes. |
Action | Specify the values for the missing attributes. |
Explanation | The specified <failoverController> element is not present in the configuration. |
Action | An internal error has occurred. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | One of the <failoverController> elements in the configuration is incomplete. The incomplete address will be ignored. |
Action | Specify the missing configuration attribute. |
Explanation | The same host and port combination was defined twice in the <collectiveMember> and/or the <failoverController> elements. |
Action | Remove the duplicate address. |
Explanation | This is can occur when the server is shutting down, if the feature is removed, or if configuration is removed. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | A connection to the collective controller has been established. |
Action | This message is for information purposes only. |
Explanation | The connection to the collective controller has been lost. |
Action | This message is for information purposes only. |
Explanation | None of the configured collective controllers could be reached. |
Action | Verify that at least one of the configured collective controllers is available. |
Explanation | The configured duration for the heartBeatInterval attribute is less than the minimum required duration. The heart beat interval has been set to the default value. |
Action | Modify the value for the heartBeatInterval attribute in the server.xml to be at least the minimum duration. |
Explanation | The configured duration for the controllerReadTimeout attribute is less than the minimum required duration. The controller read timeout has been set to the default value. |
Action | Modify the value for the controllerReadTimeout attribute in the server.xml to be at least the minimum duration. |
Explanation | The member heart beat interval is the number of seconds between member heart beats. |
Action | No action required. |
Explanation | The server has been elected as the host leader on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server has been elected as a host follower on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server is no longer the host leader on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server is no longer a host follower on the specified port. |
Action | This message is for information purposes only. No action is required. |
Explanation | The configured host leader election port has changed. |
Action | This message is for information purposes only. No action is required. |
Explanation | The host leader was deactivated or its configured port was changed and the network port used for host leader elections could not be closed. The network port is in an indeterminate state. |
Action | If host leader elections on this host and the indicated port fail, the interface may need to be reset, or a different port used. Consult FFDC logs for more information on the failure error. |
Explanation | The IP address or host name of the server could not be determined. |
Action | Check the server's network configuration. |
Explanation | The specified password cannot be correctly encoded. |
Action | Check FFDC log for the root cause of the error. |
Explanation | This message indicates the SSH keys are being generated. This action can take a few moments. |
Action | This message is for information purposes only. No action is required. |
Explanation | This message indicates the SSH keys have been successfully generated. |
Action | This message is for information purposes only. No action is required. |
Explanation | There was an error while processing or generating the SSH keys. The current user may not have permissions to write or read a specific file or directory. |
Action | Ensure the user which has started the server has the correct permissions to access the SSH files. |
Explanation | The specified algorithm is required for SSH key generation. |
Action | Change server.xml to use user generated SSH key pair or password authentication. |
Explanation | The server's host information was successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | Unable to publish the server's host information to the collective repository. |
Action | This message indicates the error which caused the publishing error. |
Explanation | The server's paths were successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | Unable to publish the server's paths to the collective repository. |
Action | This message indicates the error which caused the publishing error. |
Explanation | The server state was successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | The server may not be able to be managed remotely. |
Action | This message indicates the error which caused the publishing error. |
Explanation | sshPrivateKey and userPassword have been specified. Set either sshPrivateKey or userPassword, but not both. Key-based authentication will be used and the userPassword will be ignored. |
Action | Set either sshPrivateKey or userPassword, but not both. |
Explanation | An sshPublicKeyPath has been set without a corresponding sshPrivateKey. |
Action | Either remove the sshPublicKeyPath property or specify the corresponding sshPrivateKey. |
Explanation | The private key is required for key-based authentication. |
Action | Either remove the sshPrivateKeyPassword property or specify the corresponding sshPrivateKey. |
Explanation | The attribute useSudo for element <hostAuthInfo> is set to false, but other sudo options are set. sudo will not be used and the other options will be ignored. |
Action | Either set useSudo to true, or unset the other sudo options. |
Explanation | No credentials have been set for the <hostAuthInfo> configuration. Default SSH key configuration will be used. |
Action | This message is for information purposes only. |
Explanation | The remote host authentication has been configured successfully. |
Action | This message is for information purposes only. |
Explanation | The specified SSH public key file does not exist or is not a regular file. Check that the path is correct and that file does exist. The private key file does exist and will be used for authentication. |
Action | Check that the path is correct and that file does exist. |
Explanation | The specified SSH private key file does not exist or is not a regular file. Check that the path is correct and that file does exist. Key-based authentication can not be completed without a private key. |
Action | Check that the path is correct and that file does exist. |
Explanation | The specified key pair is incomplete. The SSH private key does not exist or is not a regular file. Check that the path is correct and that file does exist. Key-based authentication can not be completed without a private key. |
Action | Check that the path is correct and that file exists. |
Explanation | Unable to publish the JMX endpoint information for this server. This server's MBeans will not be able to be managed through the collective. A configuration or other type of warning or error has 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 | An internal error has occurred. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | No HTTP endpoint configuration was detected for the default_host virtual host within the expected time. |
Action | Configure an HTTP endpoint for the default_host virtual host. If the HTTP endpoint becomes available, the JMX endpoint information will be published. |
Explanation | A configuration error has occurred: the HTTPS port for the HTTP endpoint for default_host virtual host in server configuration is not valid or disabled. |
Action | Check that the HTTP endpoint for default_host virtual host has the HTTPS port configured and the value is valid. |
Explanation | The X509 certificate presented for authentication is not a certificate issued by a WebSphere Application Server collective. The certificate is not valid for authentication to the collective as a collective member. |
Action | The certificate was not recognized as a WebSphere Application Server collective certificate. Check the certificate used by the authenticating caller. |
Explanation | The X509 certificate presented for authentication is not a collective controller certificate issued by a WebSphere Application Server collective controller. The certificate is not valid for authentication to the collective member. |
Action | The certificate was not recognized as a WebSphere Application Server collective controller certificate. Check the certificate used by the authenticating caller. |
Explanation | The server configuration may have been copied to a new host, or the host name or the host network configuration may have changed. If the server configuration was copied, a new server identity must be generated for this server. If the host name change was intentional, the identity of the server must be regenerated. |
Action | If the server identity needs to be regenerated, remove resources/collective directory for the server and join the server to the collective with bin/collective join. |
Explanation | The server configuration may have been copied to a new user directory, or the user directory may have changed. If the server configuration was copied or the user directory was changed, a new server identity must be generated for this server. |
Action | If the server identity needs to be regenerated, remove resources/collective directory for the server and join the server to the collective with bin/collective join. |
Explanation | The name of the server does not match the name given on the collective create, join, or addReplica operation. The server configuration might have been copied to a new server directory with a different name, the server directory name might have changed, or the server name specified in the server create command and in the collective create or join command were not identical. This message appears in the log of the affected server after it starts. |
Action | If this condition occurred because the server directory name was changed, changing it back will resolve the problem. In all other cases, the server identity must be regenerated. This requires that the collective operation be repeated. First, undo the collective operation. For a member, run a collective remove command. For a controller replica, run a collective removeReplica command. If there is only one controller, no command is required. Second, remove the resources/collective directory for the server and run the collective operation again. |
Explanation | The product cannot validate the server identity. An unexpected error might have occurred during the validation sequence. |
Action | likely causes of the error are that the required keystore does not exist, the keystore does not define the required certificate, or the certificate subject DN is incorrect. |
Explanation | The remote host authentication is configured successfully. |
Action | This message is for information purposes only. |
Explanation | The administrative metadata file could not be parsed due to an error. For example, it could contain a syntax error. The exception indicates the error. |
Action | Specify the correct metadata in the admin-metadata.xml file. |
Explanation | The contents of the administrative metadata changed. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | The administrative metadata was successfully published to the collective repository. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | The admin-metadata.xml file must specify administrative metadata correctly for a successfully publication of the metadata to the collective repository. The metadata might not be correct. |
Action | Ensure the administrative metadata is correct. |
Explanation | An internal error occurred when deploying the administrative metadata to the collective repository. |
Action | Try the operation again. |
Explanation | The publication of administrative runtime metadata was successful. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | The product cannot publish the administrative metadata because the AdminMetadataManager MBean operation is in an incompatible collective controller. |
Action | Ensure the member is connecting to a compatible level of the collective controller. |
Explanation | The application {0} cannot be published because the product cannot find it in the collective repository. The application might not be installed on the server or cluster. |
Action | Ensure the specified application is installed on the server or cluster. |
Explanation | The server configuration changed and the contents of the administrative metadata changed. The collective repository has the administrative metadata changes. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | The product cannot publish the administrative metadata because it was specified in the wrong location of the admin-metadata.xml file. |
Action | Check if the admin-metadata.xml file contains the correct metadata resources. |
Explanation | The administrative metadata resource has already been published. It will not be republished. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | The resource cannot be published because the product cannot find it in the collective repository. The resource might not be installed or configured. |
Action | Ensure the specified resource is installed or configured on the server. |
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 has already registered. |
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. |
Explanation | The RepositoryConfiguration MBean operation cannot be completed because required security services were unavailable to perform the authorization check. |
Action | This can occur if the server is shutting down or changing configuration at the time of the request. |
Explanation | The parameter type specified for a property is not valid. |
Action | Specify a valid parameter type for the property. |
Explanation | This is an informational message to indicate that a server has joined a cluster. |
Action | This message is for informational purposes only. No action is required. |
Explanation | This is an informational message to indicate that a server has left a cluster. |
Action | This message is for informational purposes only. No action is required. |
Explanation | This is an informational message to indicate that a cluster definition has been created in the collective. This will occur when the first member joins a cluster. |
Action | This message is for informational purposes only. No action is required. |
Explanation | This is an informational message to indicate that a cluster definition has been deleted from the collective. This will occur when the last member leaves a cluster. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The hostPaths map has a property specified which was not recognized. |
Action | Specify a supported property for the hostPaths map. |
Explanation | Life cycle event consumers might miss some events because of the error in the lifeCycleEventPublisher component. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | Before running the operation, the host must be registered or exist in the repository. |
Action | Register the host first. |
Explanation | The installation directory cannot currently be registered or exist in the repository. |
Action | Specify an installation directory that is not registered. |
Explanation | The installation directory must currently be registered or exist in the repository. |
Action | Specify an installation directory that is registered. |
Explanation | The user directory must exist in the repository. |
Action | Specify a user directory that exists in the repository. |
Explanation | The type parameter specified is not valid. The valid installable types are wlp, jre and other. |
Action | Specify a valid installable type. |
Explanation | The join command must be run to register the Java home to the repository. |
Action | Run the join command. |
Explanation | The ReplicaMonitor singleton service has elected the specified replica as the service leader. |
Action | No action required. This message is for informational purposes only. |
Explanation | The active.replicas list in the collective repository may be inaccurate due to the error in the ReplicaMonitor component. |
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 ControllerConfig MBean successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The resource type or identity must specify correctly for a successfully removal of the metadata from the collective repository. The resource type or identity might not provide correctly. |
Action | Ensure the resource type or identity information is correct. |
Explanation | An internal error occurred when undeploying the administrative metadata from the collective repository. |
Action | Try the operation again. |
Explanation | The contents of the administrative metadata were unpublished. |
Action | This message is for informational purposes only. No action is needed. |
Explanation | The AdminMetadataManager MBean successfully started and is available to process requests. |
Action | This message is for informational purposes only. No action is required. |
Explanation | --useHostCredentials cannot be used unless credentials have been established first |
Action | Register or update the host first to supply the credentials. |
Explanation | The member cannot be registered because the repository has reached its maximum number of connected members. |
Action | No action is required. The member will continue attempting to connect until it is successful. |
Explanation | There was an unexpected value stored in the repository. |
Action | The value must be manually removed using the CollectiveRepositoryMBean delete method |
Explanation | There was an unexpected configuration object stored in the repository. |
Action | The value must be manually removed using the CollectiveRepositoryMBean delete method |
Explanation | An unexpected exception occurred accessing the repository paths. |
Action | Retry the operation. |
Explanation | The deploy variable specifed is not defined in the controller server.xml. |
Action | Define the deploy variable in the controller server.xml |
Explanation | A deployment variable configuration was registered that replaced a previous configuration and changed some of the values for the variable. |
Action | This message is for informational purposes only. No action is required. |
Explanation | The cluster contains members that are not Liberty members. The operation attempted is only available to Liberty members. |
Action | Make sure that all members in the cluster are Liberty members. |
Explanation | The member connected to the controller. |
Action | No action required. The member successfully connected to the controller. |
Explanation | The member disconnected from the controller. |
Action | No action required. The member successfully disconnected from the controller. |
Explanation | The member missed 3 heart beats, causing a forced deregistration. |
Action | Address the liveness of the member and reconnect if necessary. |
Explanation | The collective.uuid file could not be found. |
Action | Run WLP_INSTALL_DIR/bin/collective create to initialize this server to be a collective controller. |
Explanation | The collective.uuid file is not a regular file, it may be a non-standard file or a directory. |
Action | Run WLP_INSTALL_DIR/bin/collective create to initialize this server to be a collective controller. |
Explanation | The collective.uuid file is not in the expected format. |
Action | Run WLP_INSTALL_DIR/bin/collective create to initialize this server to be a collective controller. |
Explanation | The collective.uuid file contents is not in the expected format. |
Action | Run WLP_INSTALL_DIR/bin/collective create to initialize this server to be a collective controller. |
Explanation | The X509 certificate presented for authentication is not a certificate issued by a WebSphere Application Server collective. The certificate is not valid for authentication to the collective as a collective member. |
Action | The certificate was not recognized as a WebSphere Application Server collective certificate. Check the certificate used by the authenticating caller. |
Explanation | The X509 certificate presented for authentication is not a certificate issued by this WebSphere Application Server collective. The certificate is not valid for authentication to this collective. |
Action | The certificate was not recognized as a WebSphere Application Server collective certificate issued by this collective. Check the certificate used by the authenticating caller. |
Explanation | The X509 certificate presented for authentication is for a collective member that is currently flagged for NOLOGIN. |
Action | If the member should be allowed to login, remove the NOLOGIN flag for the member. |
Explanation | The identified collective member attempted to access a resource which it was not permitted to access. |
Action | Ensure the collective member has the correct host name, user directory and server name. If the host name, user directory and server name are not correct, the configuration of the server may have changed and the member may need to obtain a new collective security configuration. |
Explanation | The identified collective member attempted to perform an operation which it was not permitted to perform. |
Action | The operation that was attempted to be performed is not permitted for collective members. |
Explanation | The identified collective member attempted to perform an operation which it was not permitted to perform. |
Action | The operation that was attempted to be performed is not permitted for collective members. |
Explanation | The collective.name file is empty or not a file. |
Action | Specify the --collectiveName option for WLP_INSTALL_DIR/bin/collective create to establish a collective name when creating a collective. If the collective exists, create the server/resources/collective/collective.name file and set the contents to the desired UTF-8 encoded name. |
Explanation | The data stored in collective.name is longer than allowed. The collective name must be less than 2048 bytes. |
Action | Reduce the length of the name for the collective. |
Explanation | The server detected a change to the collective name. This change might not be intentional. |
Action | If the change to the collective name was intentional, no action is required. Otherwise, you can change the name by changing the value of the server/resources/collective/collective.name file. |
Explanation | The server cannot store the collective name in the repository. The server will try to store the name during the next server start. |
Action | No action is required. |
Explanation | Host level SingletonServiceMessenger MBean operations cannot be completed across different host systems, but only within a host system. |
Action | The operation that was attempted to be performed is not permitted. |