Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Chains must contain transport channels to function. |
Action | Add some transport channels to the specified chain. |
Explanation | Transport channels can flow into a server (inbound channels) or out of a server (outbound channels). All transport channels in a chain must flow in the same direction. |
Action | Ensure that all of the transport channels in the chain flow in the same direction. Do not mix inbound and outbound channels in the same chain. |
Explanation | The first transport channel in an in inbound chain must be a connector channel. |
Action | Ensure that the first transport channel in the inbound chain is a connector channel. |
Explanation | The last transport channel in an inbound chain must be an acceptor channel. |
Action | Ensure that the last transport channel in the inbound chain is an acceptor channel. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Channels must provide a descriptor to map configuration types to runtime types; no matching descriptor could be found. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Transport Channel Service has started the specified chain. |
Action | No action needed. |
Explanation | The Transport Channel Service has stopped the specified chain. |
Action | No action needed. |
Explanation | Inbound chains must be explicitly marked as enabled to be eligible for automatic startup. Disabled chains can still be started, but they must be explictly started by name. |
Action | No action needed. |
Explanation | The Transport Channel Service generated an exception when attempting to discover and load its configuration. It will be started without configuration. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Transport Channel Service could not locate its configuation. The default configuration details for the Transport Channel Service should be added to the server.xml configuration file. |
Action | Use the administrative console or wsadmin to add default configuration for the Transport Channel Service. |
Explanation | The Transport Channel Service has been explicitly configured to be disabled and will not be started. |
Action | No action needed. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Channels must provide a descriptor to map configuration types to runtime types. No matching descriptor could be found. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The last transport channel in an outbound chain must be a connector channel. |
Action | Ensure that the last transport channel in the outbound chain is a connector channel. |
Explanation | An exception was generated in either the chain or the underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | An exception was generated in either the chain or the underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | An exception was generated in either the chain or the underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | An exception was generated in either the chain or the underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | The configured number of retries is not enough to cause the chain to start, or the port used by the chain is already in use. |
Action | Ensure the port used by the chain is not already in use. Correctly set the custom properties for restarting chains. |
Explanation | The initial attempt to start the chain did not succeed. Further attempts will be made to get it started. |
Action | Watch for an error or audit message indicating the result of the retry attempts. |
Explanation | The value of the property is out of the expected bounds. |
Action | Adjust the configuration to set the property to a valid value. |
Explanation | The runtime environment does not contain a channel factory of the matching type, and so cannot start the chains that use it. |
Action | Check whether the runtime featureset list is missing one or more required items. |
Explanation | An error was encountered while creating the default configuration for TCP channnels. |
Action | Review the exception for information on how the creation failed. |
Explanation | An error was encountered while creating the default configuration for UDP channnels. |
Action | Review the exception for information on how the creation failed. |
Explanation | The channel has been configured to be a non-shareable channel. However the channel is being shared between multiple regions. |
Action | Review the configuration of the channel and its usage. |
Explanation | No additional information. |
Action | Correct the configuration error. |
Explanation | No additional information. |
Action | Correct the configuration error. |
Explanation | Each entry in the list must be a valid String. |
Action | Correct the configuration error. |
Explanation | Each entry in the list must be a valid String. |
Action | Correct the configuration error. |
Explanation | Each entry in the list must be a valid String. |
Action | Correct the configuration error. |
Explanation | Each entry in the list must be a valid String. |
Action | Correct the configuration error. |
Explanation | A custom property was specified with a value that is outside the range of valid values. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel property value is not a valid number. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel property value is not within the valid range for this property. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel property value is not within the valid range for this property. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel property value is not within the valid range for this property. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel property value is not within the valid range for this property. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel property has a name or value that has not been recognized. |
Action | Correct the configuration error. |
Explanation | A custom property was specified incorrectly. |
Action | Correct the configuration error. |
Explanation | During an attempt to update the configuration, a TCP Channel property was given a new value. However, this property cannot be updated with a new value at run time. |
Action | Correct the configuration error. |
Explanation | The specified TCP Channel could not be updated because the new configuration was not a valid configuration. |
Action | Correct the configuration error. |
Explanation | No additional information. |
Action | Correct the configuration error. |
Explanation | After starting, the system was configured to switch to a user ID that was not valid. |
Action | Change configured user id to a new value. |
Explanation | After starting, the system was configured to switch to a group ID that was not valid. |
Action | Change configured group id to a new value. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The socket bind operation did not succeed. A common cause is that the port number is already in use. Check the Exception Message text in the error message for more information. |
Action | Check that the TCP Channel has been configured to use the correct port number. |
Explanation | The specified TCP Channel has exceeded the maximum number of open connections and is refusing some connections. |
Action | If more connections are required, update the maximum number of connections allowed. |
Explanation | The specified TCP Channel could not obtain a thread from the thread pool, so processing of additional requests might be delayed. |
Action | If the CPU is not fully utilized, increase the maximum number of threads in the thread pool. Otherwise, reduce the number of incoming requests. |
Explanation | The host name specified could not be resolved. The host name was specified incorrectly or has not been defined on this system. |
Action | Check that the TCP Channel has been configured to use the correct host name. |
Explanation | The specified TCP Channel can no longer accept connections for a port. The port appears to be disabled. |
Action | To use the port, enable the port then restart the application. |
Explanation | TCP requires the Event service to be available in order to complete socket IO. |
Action | Ensure the Event service is working. |
Explanation | TCP requires an Executor service to be available in order to complete socket IO. |
Action | Ensure the "threading" bundle is active. |
Explanation | The server has stopped accepting connections due to a large number of exceptions. This might indicate a problem in your JVM or operating system. The server will try accepting connections in 10 minutes. |
Action | Examine the message and exception logs for connection or file handle errors. The server may need to be restarted. If the problem persists, please contact IBM support. |
Explanation | The Asynchronous TCP/IP sockets I/O for Liberty (AsyncIO) on z/OS service, which provides basic capabilities of an Asynchronous I/O package at the operating system level, is activated. |
Action | No action is required. |
Explanation | The Asynchronous TCP/IP sockets I/O for Liberty (AsyncIO) on z/OS service, which provides basic capabilities of an Asynchronous I/O package at the operating system level, is activated. |
Action | No action is required. |
Explanation | The Asynchronous TCP/IP sockets I/O for Liberty (AsyncIO) on z/OS service, which provides basic capabilities of an Asynchronous I/O package at the operating system level, is deactivated. |
Action | No action is required. |
Explanation | The Asynchronous TCP/IP sockets I/O for Liberty (AsyncIO) on z/OS service, which provides basic capabilities of an Asynchronous I/O package at the operating system level, is deactivated. |
Action | No action is required. |
Explanation | The UDP Channel has successfully started. |
Action | No action is required. |
Explanation | The UDP Channel has stopped normally. |
Action | No action is required. |
Explanation | Configuration values are being ignored by the UDP channel. |
Action | No action is required. |
Explanation | The system cannot resolve the configured hostname. |
Action | Verify that the hostname configuration is correct. |
Explanation | The configured port might already be in use. |
Action | Verify that the port configuration is correct. |
Explanation | The UDP Channel attempted to send a packet to a host whose hostname cannot be resolved. The DNS server might not be running, or might be mis-configured. |
Action | Verify that the DNS configuration for the server is correct. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A custom property was specified with a value that is outside the range of valid values. |
Action | Correct the configuration error. |
Explanation | A custom property was specified incorrectly. |
Action | Correct the configuration error. |
Explanation | A WsByteBuffer configuration property value is not a valid number. |
Action | Correct the configuration error. |
Explanation | The pool sizes or pool depths were specified incorrectly. |
Action | Correct the configuration error. |
Explanation | One or more settings for security in the SSL channel were not valid. |
Action | The SSL channel security settings should be modified to the correct values. |
Explanation | A new connection failed to complete a successful secure handshake. The most common reason is that the client sent an unencrypted message to a secure port. Another common reason is that an SSL certificate expired. |
Action | If the client sent an unencrypted message to a secure port, configure the client to use SSL, or to connect to a port on the application server that does not require SSL. Alternatively, check whether an SSL certificate expired. If it has, replace the expired SSL certificate with an unexpired one. |
Explanation | An error was encountered while attempting to initialize the SSL bundle. This is likely due to a dependency failure. |
Action | Review the process logs for information on what failed to start. |
Explanation | An error was encountered while creating the default configuration for SSL channnels. |
Action | Review the exception for information on how the creation failed. |
Explanation | The number of SSL handshake failures that are logged are limited to avoid excessive log entries. |
Action | No action is required. |
Explanation | An attempt was made to access a URL that did not match any of the registered handlers. |
Action | Correct the URL to match a registered handler. |
Explanation | This internal server error is thrown because the specified service is not available. |
Action | Restart the server with the clean option. |
Explanation | An SSL context could not be created with the member's SSL certificate. |
Action | Check the collective's SSL configuration, including the controller and target member. |
Explanation | The specified required parameter is missing from the request. |
Action | Include the specified parameter in the request and retry the request. |
Explanation | The specified required header is missing from the request. |
Action | Include the specified header in the request and retry the request. |
Explanation | The request contains an input field with an incorrect value. The input field does not match any records in the system. |
Action | Correct the value of the input field and retry the request. |
Explanation | The server is unable to consume the MIME type of the request. The MIME type does not match any of the expected MIME types. |
Action | Correct the value of the content type and send the request again. |
Explanation | The specified service is not available. This is an internal server error. |
Action | Restart the server with the [--clean] option. |
Explanation | The server failed to create the specified file. This could impact the ability to describe RESTful APIs. |
Action | Check that the directory exists and that the server has write access to it. Alternatively, restart the server using the --clean option. |
Explanation | The server failed to create the specified file. This could impact the ability to describe RESTful APIs. |
Action | Check that the directory exists and that the server has write access to it. Alternatively, restart the server using the --clean option. |
Explanation | The APIProvider returned a null or empty document. The APIProvider either does not support the specified document type or cannot provide one due to some internal error. |
Action | Return a valid document. |
Explanation | The server failed to copy the OpenAPI YAML file to the specified location. |
Action | Check that the server has write access to the specified directory and there is sufficient disk space for this file. |
Explanation | The server failed to copy the Swagger JSON file to the specified location. |
Action | Check that the server has write access to the specified directory and there is sufficient disk space for this file. |
Explanation | Probably due to a valid error, a Swagger object cannot be created for the APIProvider. |
Action | Provide a valid document. |
Explanation | The server failed to create the specified file. This could impact the ability to describe RESTful APIs. |
Action | Check that the directory exists and that the server has write access to it. Alternatively, restart the server using the --clean option. |
Explanation | A Swagger object created for the APIProvider was null, probably due to a valid error. |
Action | Provide a valid document. Inspect the logs to discover the error. |
Explanation | The server failed to copy the Swagger JSON file to the specified location. |
Action | Check that the server has write access to the specified directory and there is sufficient disk space for this file. |
Explanation | The server cannot find the Swagger file at the context root, probably because the Swagger file was not provided with the application. |
Action | Provide a valid Swagger file at the context root. |
Explanation | The specified service is not available. This is an internal server error. |
Action | Restart the server with the "--clean" option. |
Explanation | The public URL cannot be set to a value that has been reserved for use by the application server. |
Action | Specify a valid value for the publicURL attribute in the server configuration. |
Explanation | A Swagger object that was created for the Swagger definition is null. |
Action | Inspect the logs to find the error. Provide a valid Swagger document for the swaggerDefinition. |
Explanation | There are more than one provided Swagger documents with Swagger definitions defined in them. |
Action | Specify a swaggerDefinition in the server configuration or resolve the conflicting information in the provided Swagger documents. |
Explanation | The CSS document that is specified does not contain [.swagger-section #header], or it is not formatted to meet the constraints that are required by the server. |
Action | Provide a valid CSS file that contains a [.swagger-section #header] in the required format. |
Explanation | Probably due to a valid error, a CSS document cannot be processed. |
Action | Provide a valid CSS document. |
Explanation | The server cannot process the custom CSS file that was specified by using the x-ibm-css field within the Swagger Info object. The server will restore the default values for the Swagger UI. |
Action | Provide a valid custom CSS file for the Swagger UI along with all the dependencies. |
Explanation | The value of the specified property is either invalid or is not supported by the APIDiscovery framework. |
Action | Provide a valid value for the property within the custom CSS file for the Swagger UI. |
Explanation | The background image either does not exist or is invalid. |
Action | Provide a valid image. |
Explanation | The server has reached its limit of concurrent subscriptions and cannot provide a new subscription URL until issued subscriptions are returned or the limit is increased. |
Action | Release any unused subscription clients or increase the configured subscription limit. |
Explanation | The server has reached its limit of concurrent subscriptions and cannot provide a new subscription URL until issued subscriptions are returned or the limit is increased. |
Action | Release any unused subscription clients or increase the configured subscription limit. |
Explanation | The provided reference can not be an internal reference. |
Action | Provide a valid Swagger document. |
Explanation | The Swagger specification does not allow the reference type to be prefixed. |
Action | Provide a valid Swagger document. |
Explanation | As per the Swagger specification, tag names must be unique. |
Action | Resolve the tag name conflict in the Swagger document. |
Explanation | An undefined security definition is referenced. |
Action | Define the security definition in the Swagger document. |
Explanation | Operation IDs have to be unique as per the Swagger Specifications. |
Action | Resolve the operation ID conflict in the Swagger document. |
Explanation | The provided value is not valid. |
Action | Provide a valid value. |
Explanation | The contents could not be deserialized into a tree. |
Action | Ensure the content is valid and can be converted into a JsonNode tree. |
Explanation | The contents could not be deserialized into the expected type. |
Action | Ensure the contents and the expected type are compatible. |
Explanation | Reference format in not valid. |
Action | Ensure that a valid reference is provided. |
Explanation | Only external references can be read. |
Action | Provide an external reference. |
Explanation | A file does not exist at the referenced path. |
Action | Ensure that the file exists at the specified path. |
Explanation | The provided internal reference is not valid. |
Action | Provide a valid internal reference. |
Explanation | The provided reference value is null. |
Action | Provide a valid reference. |
Explanation | The referenced definition does not exist in the file. |
Action | Ensure that the file contains the expected definition. |
Explanation | An undefined security definition is referenced. |
Action | Define the security definition in the Swagger document. |
Explanation | The required field does not exist in the parameter. |
Action | Ensure that the parameter contains the required field. |
Explanation | A null parameter in the list indicates that the Swagger document contains an invalid parameter. |
Action | Ensure that the Swagger document contains only valid parameters. |
Explanation | Only the form parameters are allowed to have a "type" field with a value of "file". |
Action | Ensure that the parameter contains a valid value for the "type" field. |
Explanation | All defined path parameters must be declared within the path. |
Action | Ensure that all defined path parameters are declared. |
Explanation | All defined path parameters must be declared within the path. |
Action | Ensure that all defined path parameters are declared. |
Explanation | All declared path parameters must be defined. |
Action | Ensure that all declared path parameters are defined. |
Explanation | There can only be one payload, hence there can only be one body parameter. The body and form parameters cannot exist together. |
Action | Ensure that the path does not define more than one body or a combination of body and form parameters. |
Explanation | There can only be one payload, hence there can only be one body parameter. The body and form parameters cannot exist together. |
Action | Ensure that the operation does not define more than one body or a combination of body and form parameters. |
Explanation | Duplicated global parameters are not allowed. |
Action | Ensure that the path does not define any duplicated parameters. |
Explanation | Duplicated parameters are not allowed within the operation. |
Action | Ensure that the operation does not define any duplicated parameters. |
Explanation | The "required" field is mandatory for path parameters and its value must be "true". |
Action | Ensure that the path parameter contains the "required" field with its value set to "true". |
Explanation | The "required" field is mandatory for path parameters and its value must be "true". |
Action | Ensure that the path parameter contains the "required" field with its value set to "true". |
Explanation | The value of the "type" field must be one of "string", "number", "integer", "boolean", "array" or "file". |
Action | Ensure that the parameter contains a valid value for the "type" field. |
Explanation | A file from the class path was not read because it is in an invalid format. |
Action | Ensure that the specified file is in a valid file format. |
Explanation | The specified file does not exist on the class path. |
Action | Ensure that the file exists on the class path. |
Explanation | The REST API documentation was successfully published to the collective repository. |
Action | This message is for information purposes only. No action is required. |
Explanation | This message indicates the error which caused the publishing error. |
Action | Analyze the error message. The error could be caused by environmental problems. |
Explanation | The specified service is not available. This is an internal server error. |
Action | Restart the server with the "--clean" option. Check the Knowledge Center for more information on the server command options. |
Explanation | Cross-origin resource sharing (CORS) is successfully configured on the collective member. The collective controller can invoke the REST API endpoints that are available on this server. |
Action | This message is for information purposes only. No action is required. |
Explanation | This internal server error is thrown because the specified service is not available. |
Action | Restart the server with the clean option. |
Explanation | The server created an internal error. The specified service is not available. |
Action | Choose the --clean option and restart the server. |
Explanation | The requested configuration element was not found in the server.xml file. |
Action | Verify that the configuration element exists in the server.xml file and that it is correctly spelled with matching case. |
Explanation | A configured element with the requested unique identifier was not found. An instance with a different unique identifier was found and is reported in case it is the one that you were looking for. |
Action | Determine the correct unique identifier. For top-level configuration elements with an ID attribute specified, the unique identifier is the value of the ID attribute. Otherwise, the unique identifier is generated by the server. |
Explanation | A unique identifier can only be used once. |
Action | Update the server configuration to add or modify the ID attributes of the configured instances so that each unique identifier is used only once. |
Explanation | When a cyclic dependency exists in the configuration, it is broken by truncating the redundant configuration detail. |
Action | No action is needed. |
Explanation | The requested type of configuration element is not provided by any of the features that are enabled. |
Action | Check that the spelling is correct and that the correct features are enabled for this configuration. |
Explanation | The specified type of configuration element does not have the ability to validate its configuration. |
Action | Do not attempt to validate this type of configuration element. |
Explanation | The validation request for the specified configuration cannot be completed. This could be due to an unsatisfied dependency, a missing feature that enables a configuration element, or the configuration element might not support validation. |
Action | Verify that the feature that provides the configuration element is enabled, there are no missing dependencies, and the configuration element supports validation. |
Explanation | The equals sign delimiter is necessary to determine which part of the X-Login-Config-Props header is the login configuration property name and which part is the value. |
Action | Update the X-Login-Config-Props header to include an equals sign (=) between the login configuration property name and value. |
Explanation | An attempt was made to access a URL that did not match any of the registered handlers. |
Action | Correct the URL to match a registered handler. |
Explanation | Validation is only possible for resource adapter connection factories that are JMS connection factories or implement javax.resource.cci.ConnectionFactory or javax.sql.DataSource. |
Action | Do not attempt to validate this type of connection factory. |
Explanation | A feature that enables JMS is required for this configuration element. |
Action | Include a feature that enables JMS in the server configuration. |
Explanation | The validation REST endpoint was unable to determine the name of the ConnectionSpec implementation, so it has no way of supplying the specified user name and password to the connection factory. |
Action | Omit the user and password parameters when requesting validation of this connection factory. |
Explanation | An attempt was made to access a URL that did not match any of the registered handlers. |
Action | Correct the URL to match a registered handler. |
Explanation | This internal server error is thrown because the specified service is not available. |
Action | Restart the server with the clean option. |
Explanation | The specified service is not available. This is an internal server error. |
Action | Restart the server with the [--clean] option. |
Explanation | An Open API object created for the OASProvider was null, probably due to a valid error. |
Action | Provide a valid document. Inspect the logs to discover the error. |
Explanation | An OpenAPI object that was created by using the customization value is null. |
Action | Inspect the logs to find the error. Provide a valid OpenAPI document for the customization attribute. |
Explanation | The Open API document is invalid. |
Action | Provide a valid Open API document. |
Explanation | Multiple Open API customization files are in the ${server.config.dir}/openapi directory. |
Action | Ensure only one default Open API customization file in the ${server.config.dir}/openapi directory. |
Explanation | The CSS document cannot be processed due to a valid error. |
Action | Provide a valid CSS document. |
Explanation | The value of the specified property is either invalid or is not supported by the OpenAPI framework. |
Action | Provide a valid value for the property within the custom CSS file for the OpenAPI UI. |
Explanation | The background image either does not exist or is invalid. |
Action | Provide a valid image. |
Explanation | The server cannot process the custom CSS file that was specified by using the x-ibm-css field within the OpenAPI Info object. The server will restore the default values for the OpenAPI UI. |
Action | Provide a valid custom CSS file for the OpenAPI UI along with all the dependencies. |
Explanation | The CSS document that is specified does not contain [.swagger-ui .headerbar ], or it is not formatted to meet the constraints that are required by the server. |
Action | Provide a valid CSS file that contains a [.swagger-ui .headerbar ] in the required format. |
Explanation | The ClassLoader fails to load a class definition for the specified class. |
Action | Ensure the class definition is provided at runtime and all required features are enabled in the server configuration. |
Explanation | An error occurred when loading the OpenAPI programming interface specified through the META-INF/services in the application. |
Action | Ensure the provider class can be found and instantiated, or the result of instantiating the class is not assignable to the service type. |
Explanation | The server found an implementation of the programming model interface for the application. |
Action | No action is required. |
Explanation | By default, applications do not have access to the OpenAPI specification third-party APIs available in Liberty. To enable this access, the application must be configured in the server.xml file. |
Action | Ensure the application is configured through the server.xml file to have access to third-party APIs available in Liberty. |
Explanation | The public URL cannot be set to a value that has been reserved for use by the application server. |
Action | Specify a valid value for the publicURL attribute in the server configuration. |
Explanation | The OpenAPI document is invalid. |
Action | Provide a valid OpenAPI document that resolves the reported error. |
Explanation | The OpenAPI document contains data that is not in the recommended format. |
Action | Provide a valid OpenAPI document that resolves the reported warning. |
Explanation | The CSS document cannot be processed due to a valid error. |
Action | Provide a valid CSS document. |
Explanation | The value of the specified property is either invalid or is not supported by the OpenAPI framework. |
Action | Provide a valid value for the property within the custom CSS file for the OpenAPI UI. |
Explanation | The background image either does not exist or is invalid. |
Action | Provide a valid image. |
Explanation | The server cannot process the custom CSS file. The server will restore the default values for the OpenAPI UI. |
Action | Provide a valid custom CSS file for the OpenAPI UI along with all the dependencies. |
Explanation | The CSS document that is specified does not contain <.swagger-ui .headerbar >, or it is not formatted to meet the constraints that are required by the server. |
Action | Provide a valid CSS file that contains <.swagger-ui .headerbar > in the required format. |
Explanation | Specified OpenAPI filter class could not be found or loaded. |
Action | Make sure that the class specified exists and implements OASFilter interface. |
Explanation | Specified OpenAPI model reader class could not be found or loaded. |
Action | Make sure that the class specified exists and implements OASModelReader interface. |
Explanation | Failed to parse OpenAPI document from META-INF folder. |
Action | Make sure that the file is in correct YAML or JSON format. |
Explanation | Generated the OpenAPI document for the specified application. It can be viewed at /openapi endpoint. |
Action | No action is required. |
Explanation | A runtime error occurred when processing the application. |
Action | Review the FFDC logs and exception text to identify the problem. |
Explanation | The OpenAPI documentation from multiple web modules cannot be successfully merged. The endpoints from the reported modules are not included in the generated OpenAPI document. |
Action | Review the merge problems to identify why the generated OpenAPI documents cannot be merged. |
Explanation | Unless OpenAPI documentation merging is enabled, OpenAPI documentation is generated only for the first OpenAPI module deployed. |
Action | If you want all of your web modules to be used to generate OpenAPI documentation, set the MicroProfile Config property that is listed in the message. That property can be set in any of the locations that MicroProfile Config searches for config properties, such as in a Java system property or an environment variable. |
Explanation | If the property is set, it must be set to a complete info section in JSON format, with the title and version properties set to valid values. |
Action | Correct the configured info value. |
Explanation | If the property is set, it must be set to a complete info section in JSON format. |
Action | Review the error text to identify the problem and correct the configured info value so that it is valid JSON. |
Explanation | The config property must contain a comma-separated list of application and module names, or one of the special values "all", "first", or "none". |
Action | Review the error text to identify the problem and correct the indicated configuration property. |
Explanation | The server is configured to create OpenAPI documentation for the application or module name, but no application or web module with that name was deployed. |
Action | Check that all applications started correctly and that the names in the configuration property are specified correctly. |
Explanation | The OpenAPI UI path is set to a value that is not the default. |
Action | No action is required. |
Explanation | The OpenAPI Document path is set to a value that is not the default. |
Action | No action is required. |
Explanation | The OpenAPI UI path is invalid. The default value is used instead. |
Action | Check earlier error messages for the cause of validation failure. |
Explanation | The OpenAPI Document path is invalid. The default value is used instead. |
Action | Check earlier error messages for the cause of validation failure. |
Explanation | The OpenAPI Document and OpenAPI UI paths cannot be the same. |
Action | Specify a unique path for the OpenAPI UI. |
Explanation | The OpenAPI UI Path cannot be set to a value that contains invalid characters. |
Action | Ensure the OpenAPI Path contains only A-Za-z0-9, _, -, ., /. |
Explanation | The OpenAPI Document Path cannot be set to a value that contains invalid characters. |
Action | Ensure the OpenAPI Path contains only A-Za-z0-9, _, -, ., /. |
Explanation | OpenAPI path segment "/." or "/.." is invalid. |
Action | Remove any path "/." or "/.." segment from the path. |
Explanation | The specified service is not available. This is an internal server error. |
Action | Restart the server with the [--clean] option. |
Explanation | An Open API object created for the OASProvider was null, probably due to a valid error. |
Action | Provide a valid document. Inspect the logs to discover the error. |
Explanation | An OpenAPI object that was created by using the customization value is null. |
Action | Inspect the logs to find the error. Provide a valid OpenAPI document for the customization attribute. |
Explanation | The public URL cannot be set to a value that has been reserved for use by the application server. |
Action | Specify a valid value for the publicURL attribute in the server configuration. |
Explanation | Multiple Open API customization files are in the ${server.config.dir}/openapi-3.1 directory. |
Action | Ensure only one default Open API customization file in the ${server.config.dir}/openapi-3.1 directory. |
Explanation | The CSS document cannot be processed due to a valid error. |
Action | Provide a valid CSS document. |
Explanation | The OpenAPI document is invalid. |
Action | Provide a valid OpenAPI document that resolves the reported error. |
Explanation | The OpenAPI document contains data that is not in the recommended format. |
Action | Provide a valid OpenAPI document that resolves the reported warning. |
Explanation | The server cannot process the custom CSS file. The server will restore the default values for the OpenAPI UI. |
Action | Provide a valid custom CSS file for the OpenAPI UI along with all the dependencies. |
Explanation | The CSS document that is specified does not contain <.swagger-ui .headerbar >, or it is not formatted to meet the constraints that are required by the server. |
Action | Provide a valid CSS file that contains <.swagger-ui .headerbar > in the required format. |
Explanation | The value of the specified property is either invalid or is not supported by the OpenAPI framework. |
Action | Provide a valid value for the property within the custom CSS file for the OpenAPI UI. |
Explanation | The background image either does not exist or is invalid. |
Action | Provide a valid image. |
Explanation | Failed to parse OpenAPI document from META-INF folder. |
Action | Make sure that the file is in correct YAML or JSON format. |