Explanation | Configuration of appState feature requires two attributes: appName and markerPath. |
Action | Please correct appState feature configuration by specifying application name and location of the file where application state should be recorded. |
Explanation | Application state listener filed to write application state at the specified location. Framework monitoring that file can not be notified of the application state change. |
Action | Please ensure that the server has write access to the location specified in appstate feature configuration. |
Explanation | The specified server name does not exist. |
Action | Provide a valid server name. |
Explanation | The name of the service configuration is incorrect or does not exist. |
Action | Correct the service configuration name, or import the service configuration using the import action. |
Explanation | The specified service configuration is not bound to the server. |
Action | Correct the service configuration name. |
Explanation | The specified service name does not exist. |
Action | Provide a valid service name. |
Explanation | The specified variable name is not supported by the service configuration. |
Action | Provide a variable name that the service configuration supports. |
Explanation | You must first log in to Bluemix to create, delete, or import service configuration. |
Action | Use the "bluemixUtility login" command to log in to Bluemix. |
Explanation | Authentication failed because the provided user name or password is incorrect. |
Action | Provide a valid Bluemix user name and password. |
Explanation | The specified space does not exist. |
Action | Provide a valid space name. |
Explanation | The specified organization does not exist. |
Action | Provide a valid organization name. |
Explanation | An unexpected error occurred when performing a Bluemix operation. |
Action | None. |
Explanation | The specified service plan does not exist. |
Action | Provide a valid service plan name. |
Explanation | The specified service offering does not exist. |
Action | Provide a valid service offering name. |
Explanation | The space name is not set. |
Action | Use the "bluemixUtility switch" command to set the space name. |
Explanation | The organization name is not set. |
Action | Use the "bluemixUtility switch" command to set the organization name. |
Explanation | The provided API endpoint is not a valid Bluemix endpoint. |
Action | Provide a valid Bluemix API endpoint. |
Explanation | The provided API endpoint is not a valid web address. |
Action | Provide a Bluemix API endpoint that is a valid web address. |
Explanation | The provided API endpoint is not an HTTPS or HTTP web address. |
Action | Provide a Bluemix API endpoint that is either an HTTPS or HTTP web address. |
Explanation | An unexpected error occurred while communicating with the configuration service. |
Action | Retry the operation. |
Explanation | To import service configuration, the service must have at least one service key. |
Action | Create a service key for the service. |
Explanation | The specified service key does not exist. |
Action | Provide a valid service key name. |
Explanation | An unexpected error occurred while trying to obtain variable information from service.xml file. |
Action | None. |
Explanation | An unexpected error occurred while performing service registry operation. |
Action | None. |
Explanation | The directory was not created because permission was denied. |
Action | Check file permissions. |
Explanation | A file must be created in a base directory. |
Action | None. |
Explanation | An unexpected error occurred while reading the configuration for a service. |
Action | Check file permissions. |
Explanation | An unexpected error occurred while writing the configuration for a service. |
Action | Check file permissions. |
Explanation | An error occurred while encoding password information. |
Action | Check encoding algorithm and encoding key parameters. |
Explanation | The host name of the configuration service was not resolved. |
Action | Check DNS settings, and retry the operation. |
Explanation | The connection to the configuration service was not established. The service might be temporarily down. |
Action | Check the network connection, and retry the operation. |
Explanation | A connection or read timeout error occurred when communicating with the configuration service. |
Action | Check the network connection, and retry the operation. |
Explanation | There is no route to the configuration service. |
Action | Check firewall settings, and retry the operation. |
Explanation | The host name was not resolved. |
Action | Check DNS settings, and retry the operation. |
Explanation | The connection could was not established. |
Action | Check the network connection, and retry the operation. |
Explanation | A connection or read timeout error occurred when downloading a file. |
Action | Check the network connection, and retry the operation. |
Explanation | There is no route to the host. |
Action | Check firewall settings, and retry the operation. |
Explanation | An error occurred while downloading a file. |
Action | Check the network settings, and retry the operation. |
Explanation | The host name of the Bluemix API endpoint was not resolved. |
Action | Check DNS settings, and retry the operation. |
Explanation | The connection to the Bluemix was not established. |
Action | Check the network connection, and retry the operation. |
Explanation | A connection or read timeout error occurred when communicating with Bluemix. |
Action | Check the network connection, and retry the operation. |
Explanation | There is no route to Bluemix. |
Action | Check firewall settings, and retry the operation. |
Explanation | The configuration service did not generate a configuration for the specified service. |
Action | Ensure that a valid service name, type, credential name, or parameters are specified. |
Explanation | The configuration service did not return a list of supported services. |
Action | Retry the operation. |
Explanation | Cannot create a service with a name that is already being used by another service. |
Action | Run the "bluemixUtility listServices" command to see the current services. Delete the existing service or choose another service name. |
Explanation | An instance of the service is automatically provided by the Bluemix platform. |
Action | None. |
Explanation | An instance of the service is automatically provided by the Bluemix platform. |
Action | None. |
Explanation | The server has registered itself. |
Action | No action is required. |
Explanation | The server has registered itself. |
Action | No action is required. |
Explanation | An exception occurred when registering the server. Server registration will be retried later. |
Action | No action is required. |
Explanation | An exception occurred when registering the server. Server registration will be retried later. |
Action | No action is required. |
Explanation | An error was returned when registering the server. Server registration will be retried later. |
Action | No action is required. |
Explanation | An error was returned when registering the server. Server registration will be retried later. |
Action | No action is required. |
Explanation | An exception occurred when registering the server. |
Action | See the previous messages to determine why the server did not register. |
Explanation | An exception occurred when registering the server. |
Action | See the previous messages to determine why the server did not register. |
Explanation | Application service returned an error during registration. |
Action | See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | Application service returned an error during registration. |
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 missing attribute is required in the server.xml file or to one of its referenced configuration files. |
Action | Add the attribute to the server.xml file or to one of its referenced configuration files. |
Explanation | The missing attribute is required in the server.xml file or to one of its referenced configuration files. |
Action | Add the attribute to the server.xml file or to one of its referenced configuration files. |
Explanation | The server did not process the product version files and the productInsights feature did not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server did not process the product version files and the usageMetering feature did not start. |
Action | Check that the product has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server installation is missing required files and the productInsights feature did not start. |
Action | Check that the product has an international program license agreement (IPLA) and has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server installation is missing required files and the usageMetering feature did not start. |
Action | Check that the product has an international program license agreement (IPLA) and has been installed correctly. If the problem persists, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server encountered an exception when processing one of the product information files. |
Action | Verify that the product has been installed correctly. |
Explanation | The server encountered an exception when processing one of the product information files. |
Action | Verify that the product has been installed correctly. |
Explanation | The productInsights feature encountered an exception when collecting product usage. |
Action | No action is required. |
Explanation | The usageMetering feature encountered an exception when collecting product usage. |
Action | No action is required. |
Explanation | The productInsights feature was unable to collect product usage given the environment. |
Action | No action is required. |
Explanation | The usageMetering feature was unable to collect product usage given the environment. |
Action | No action is required. |
Explanation | The productInsights feature was unable to run the specified program because of the given exception. |
Action | No action is required. |
Explanation | The usageMetering feature was unable to run the specified program because of the given exception. |
Action | No action is required. |
Explanation | The productInsights feature was unable to register with the service because the API Key was incorrect. |
Action | Update the server configuration to have the correct API Key for the service. |
Explanation | The usageMetering feature was unable to register with the service because the API Key was incorrect. |
Action | Update the server configuration to have the correct API Key for the service. |
Explanation | The productInsights feature was unable to register with the service because the SSL configuration is incorrect. |
Action | Update the server configuration to have the correct SSL settings. |
Explanation | The usageMetering feature was unable to register with the service because the SSL configuration is incorrect. |
Action | Update the server configuration to have the correct SSL settings. |
Explanation | The productInsights feature was unable to register with the service because a <productInsights> element is malformed. |
Action | Update the server configuration <productInsights> element. |
Explanation | The usageMetering feature was unable to register with the service because a <usageMetering> element is malformed. |
Action | Update the server configuration <usageMetering> element. |
Explanation | Https is the only supported protocol for the <productInsights> element url. |
Action | Change the <productInsights> element url to use https for the protocol. |
Explanation | Https is the only supported protocol for the <usageMetering> element url. |
Action | Change the <usageMetering> element url to use https for the protocol. |
Explanation | The productInsights group names can contain only letters, numbers, hyphens (-), periods (.), colons (:), and underscores (_). |
Action | In the server configuration, change the name specified on the groups attribute of the productInsights element so that it only contains valid characters. |
Explanation | The usageMetering group names can contain only letters, numbers, hyphens (-), periods (.), colons (:), and underscores (_). |
Action | In the server configuration, change the name specified on the groups attribute of the usageMetering element so that it only contains valid characters. |
Explanation | The productInsights group names cannot start with WAS_ because this term is reserved. |
Action | In the server configuration, remove WAS_ from the group names specified on the groups attribute of the productInsights element. |
Explanation | The usageMetering group names cannot start with WAS_ because this term is reserved. |
Action | In the server configuration, remove WAS_ from the group names specified on the groups attribute of the usageMetering element. |
Explanation | Groups in the productInsights element cannot be parents of themselves. |
Action | In the server configuration, change the groups specified on the productInsights element so that no group is a parent of itself. |
Explanation | Groups in the usageMetering element cannot be parents of themselves. |
Action | In the server configuration, change the groups specified on the usageMetering element so that no group is a parent of itself. |
Explanation | Groups in the productInsights element must have unique names. |
Action | In the server configuration, change the groups specified on the productInsights element so that each group name is unique. |
Explanation | Groups in the usageMetering element must have unique names. |
Action | In the server configuration, change the groups specified on the usageMetering element so that each group name is unique. |
Explanation | The SSL configuration needed for product insights is missing. |
Action | Configure SSL for product insights. |
Explanation | The SSL configuration needed for usageMetering is missing. |
Action | Configure SSL for usageMetering. |
Explanation | The SSL configuration for the productInsights feature references a keystore file that is configured in the trustStore property. The SSL configuration is referenced by the sslRef property of productInsights. If both the trustStore and the sslRef properties are not defined, the productInsights feature uses the specified keystore file from IBM Cloud Public. |
Action | No action is required. |
Explanation | The SSL configuration for the usageMetering feature references a keystore file that is configured in the trustStore property. The SSL configuration is referenced by the sslRef property of usageMetering. If both the trustStore and the sslRef properties are not defined, the usageMetering feature uses the specified keystore file from IBM Cloud Public. |
Action | No action is required. |
Explanation | The SSL configuration for the productInsights feature references a keystore file that is configured in trustStore. The SSL configuration is referenced by sslRef property of productInsights. The SSL configuration for the productInsights feature requires either a definition for the sslRef or trustStore property, but not both. |
Action | Remove either the sslRef or trustStore property from the productInsights configuration. |
Explanation | The SSL configuration for the usageMetering feature references a keystore file that is configured in trustStore. The SSL configuration is referenced by sslRef property of usageMetering. The SSL configuration for the usageMetering feature requires either a definition for the sslRef or trustStore property, but not both. |
Action | Remove either the sslRef or trustStore property from the usageMetering configuration. |
Explanation | The productInsights trustStore property in the server configuration referenced a keystore file that does not exist. |
Action | Install the keystore file at the target location, or update the productInsights trustStore configuration. |
Explanation | The usageMetering trustStore property in the server configuration referenced a keystore file that does not exist. |
Action | Install the keystore file at the target location, or update the usageMetering trustStore configuration. |
Explanation | The application server process does not have read access privileges for the keystore file that is referenced in the productInsights trustStore configuration. |
Action | Update the file access privileges for the keystore file to grant read privileges to the application server process. |
Explanation | The application server process does not have read access privileges for the keystore file that is referenced in the usageMetering trustStore configuration. |
Action | Update the file access privileges for the keystore file to grant read privileges to the application server process. |
Explanation | The productInsights httpsProtocol referenced a protocol that is not valid. |
Action | Change the productInsights httpsProtocol to a valid value. |
Explanation | The usageMetering httpsProtocol referenced a protocol that is not valid. |
Action | Change the usageMetering httpsProtocol to a valid value. |
Explanation | The property value is not valid and is ignored. |
Action | Change the value of the property to a data type of integer or float. |
Explanation | The property value is not valid and is ignored. |
Action | Change the value of the property to a data type of integer or float. |
Explanation | The com.ibm.websphere.cloud.productinsights.availableProcessorsOverride property was used to override the value of the available processors metric. |
Action | No action is required. |
Explanation | The com.ibm.websphere.usage.metering.availableProcessors property was used to override the value of the available processors metric. |
Action | No action is required. |
Explanation | The productInsights feature requires a metric type with a metric definition for all metric values reported. Metrics values reported without a type or definition will be ignored. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The usageMetering feature requires a metric type with a metric definition for all metric values reported. Metrics values reported without a type or definition will be ignored. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The metric value is not valid and is ignored. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The metric value is not valid and is ignored. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The productInsights feature encountered an exception when sending product usage. |
Action | No action is required. |
Explanation | The usageMetering feature encountered an exception when sending product usage. |
Action | No action is required. |
Explanation | The productInsights feature encountered an exception when collecting product usage from a product. Its usage is not sent. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The usageMetering feature encountered an exception when collecting product usage from a product. Its usage is not sent. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The productInsights feature encountered an exception when resetting usage data collection for a product. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The usageMetering feature encountered an exception when resetting usage data collection for a product. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The productInsights feature encountered an exception when enabling usage data collection for a product. It's usage will not be sent. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The usageMetering feature encountered an exception when enabling usage data collection for a product. It's usage will not be sent. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The productInsights feature could not set a registration listener for a product and product changes do not cause a re-registration. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The usageMetering feature could not set a registration listener for a product and product changes do not cause a re-registration. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The productInsights feature encountered a problem obtaining registration information from a product and this information will be missing from registration. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The usageMetering feature encountered a problem obtaining registration information from a product and this information will be missing from registration. |
Action | See the problem determination information for the product identified in the message. |
Explanation | The productInsights feature is unable to communicate with the cloud service. |
Action | Determine the root cause of the communication problem, such as an incorrect URL in the Liberty Product Insights feature configuration, lack of internet connection, unavailable cloud service, or proxy tunneling failure. |
Explanation | The usageMetering feature is unable to communicate with the cloud service. |
Action | Determine the root cause of the communication problem, such as an incorrect URL in the usageMetering feature configuration, lack of internet connection, unavailable cloud service, or proxy tunneling failure. |
Explanation | The productInsights feature was unable to stop or cancel a task. The task can continue to run which might cause product insights to report duplicate values. |
Action | If the warning occurred during server shutdown, then no actions need to be taken. If the warning occurred outside of server shutdown, then restarting the server fixes any repercussions from this warning. |
Explanation | The usageMetering feature was unable to stop or cancel a task. The task can continue to run which might cause usageMetering to report duplicate values. |
Action | If the warning occurred during server shutdown, then no actions need to be taken. If the warning occurred outside of server shutdown, then restarting the server fixes any repercussions from this warning. |
Explanation | Because the productInsights feature ran its usage task too late to collect accurate metrics, the feature resets the usage interval and discards any metric data since the last successful collection interval. |
Action | If the usage task is running late, ensure the server process does not go to sleep while running productInsights. |
Explanation | Because the usageMetering feature ran its usage task too late to collect accurate metrics, the feature resets the usage interval and discards any metric data since the last successful collection interval. |
Action | If the usage task is running late, ensure the server process does not go to sleep while running usageMetering. |
Explanation | The value of the configuration attribute for the element is not a supported value. The configuration value is ignored. |
Action | Set the attribute to an allowed value or remove the attribute. |
Explanation | The value of the configuration attribute for the element is not a supported value. The configuration value is ignored. |
Action | Set the attribute to an allowed value or remove the attribute. |
Explanation | The missing attribute is required in the server.xml file or other configuration files. Alternatively, you can set an environment variable, CONTAINER_HOST. If you set CONTAINER_HOST, then you do not need to set workload. However, one of them is required. |
Action | Add the attribute to the configuration. Alternatively, you can set the environment variable CONTAINER_HOST. |
Explanation | The missing attribute is required in the server.xml file or other configuration files. Alternatively, you can set an environment variable, CONTAINER_HOST. If you set CONTAINER_HOST, then you do not need to set workload. However, one of them is required. |
Action | Add the attribute to the configuration. Alternatively, you can set the environment variable CONTAINER_HOST. |
Explanation | The attribute is not allowed for the current configuration settings. The configuration value is ignored. |
Action | Remove the attribute or change your configuration settings. |
Explanation | The attribute is not allowed for the current configuration settings. The configuration value is ignored. |
Action | Remove the attribute or change your configuration settings. |