Explanation | The close for the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the input stream for the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | Opening an InputStream for the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The file could not be converted to the new type object. |
Action | No user action is available. |
Explanation | Opening an InputStream for the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The resource was not found in the root container. |
Action | Verify that the resource path for the class does exist in the container. |
Explanation | An attempt to close the InputStream for the class caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | Annotation scanning was invoked for the target directory, but no class files were found there. |
Action | Check that the directory should contain classes. Remove empty directories from the application. |
Explanation | The resource was expected to be a file, but was determined to be a directory. |
Action | No user action is available. |
Explanation | The attempt to open an InputStream for the file caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the InputStream for the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The file was being opened as a JarFile and that action caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | An internal error has occurred. The count of active users for the jar file does not match the state of the jar file. |
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 | An attempt to close the JarFile object caused an exception to occur. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | There was an entry detected for the class in the jar file, but the creation of an InputStream for the class caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | An InputStream close for the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A matching method can not be found for a parameter on a coded annotation. |
Action | No user action is available. |
Explanation | A class info object for the class already exists in the cache. |
Action | No user action is available. |
Explanation | A class info object for the class already exists in the cache. |
Action | No user action is available. |
Explanation | A class info object for the class already exists in the cache. |
Action | No user action is available. |
Explanation | A class info object for the class already exists in the cache. |
Action | No user action is available. |
Explanation | The scan of a class for annotations caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A method object for the class already exists in the cache. |
Action | No user action required. |
Explanation | A field object for the class already exists in the cache. |
Action | No user action required. |
Explanation | The annotation scan process could not resolve the class. This may be resolved by a later attempt to resolve the class. |
Action | Verify that the class is included in the application or the application class path. |
Explanation | The open of a class source caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of a class source caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | When the annotation scan process tried to open an input stream for the class, an exception occurred. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | When the annotation scan process tried to close an input stream for the class, an exception occurred. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The annotation scan process was creating a ClassReader to process the input stream for the resource, and that caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | An error occurred while processing an annotation, the visitor object is incorrect |
Action | This exception is unexpected. The cause is not immediately known. |
Explanation | An internal error occurred. During the reset of the visitor, residual data was 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 | An internal error occurred. During the reset of the visitor, residual data was 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 | An internal error occurred. During the reset of the visitor, residual data was 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 | An internal error occurred. During the reset of the visitor, residual data was 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 | An internal error occurred. During the reset of the visitor, residual data was 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 | An internal error occurred. During the reset of the visitor, residual data was 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 | An internal error occurred. During annotation scan processing an object could not be created. |
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 | An internal error occurred. During annotation scan processing an object could not be created. |
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 | An internal error occurred. During annotation scan processing an object could not be created. |
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 | An error occurred while scanning class and annotations data. The associated module may function incorrectly. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A problem occurred while concluding the write of class and annotations data. The cache of class and annotations data may be incomplete and should be cleared. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A problem occurred while reading class and annotations data. Further processing may produce incorrect results as incomplete data has been read. The cache of class and annotations data should be cleared. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A problem occurred while writing of class and annotations data. The displayed line was not successfully written to the class and annotations data. The cache of class and annotations data may be incomplete and should be cleared. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A problem occurred while attempting to scan a class for class information and for annotations information. Review the displayed class to ensure that it can be read and that it contains valid class bytes. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A problem occurred while preparing a class byte code reader. The byte code values for that class may be non-valid, or the class file may not be readable. As a result, the class and annotations information for that class will not be available, and the module which uses the class may function incorrectly. |
Action | Review the contents of the class file which causes the error. If necessary, replace the class file with one with valid byte codes. Also, see the exception and the associated FFDC message for more information. |
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 | The value has non-valid contents for its expected use. The value may not be processed correctly. The associated module may function incorrectly. |
Action | The data of the module should be examined to verify that the supplied value is valid. |
Explanation | The value has non-valid contents for its expected use. The value may not be processed correctly. The associated module may function incorrectly. |
Action | The data of the module should be examined to verify that the supplied value is valid. |
Explanation | The value has non-valid contents for its expected use. The value may not be processed correctly. The associated module may function incorrectly. |
Action | The data of the module should be examined to verify that the supplied value is valid. |
Explanation | The value has non-valid contents for its expected use. The value may not be processed correctly. The associated module may function incorrectly. |
Action | The data of the module should be examined to verify that the supplied value is valid. |
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 | An exception occurred when trying to close the resource. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | A problem occurred when reading a class file to determine whether there were any annotations of interest. The class is likely to be an invalid class file. As a result, annotations from this class will not be recognized. |
Action | The class can be replaced, removed or this message ignored depending on how important the class is to the function of the application. |
Explanation | The open of the child class source caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the child class source caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The processing of class information read from an entry caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the entry caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The processing of class information read from a file caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the file caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The processing of class information read from a JAR entry caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the file caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The processing of class information read from a resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The close of the resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The file could not be converted to the new type object. |
Action | No user action is available. |
Explanation | The entry could not be converted to the new type object. |
Action | No user action is available. |
Explanation | The processing of Jandex information of a class caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The attempt to open the Jandex index resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The attempt to read the Jandex index failed with an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The attempt to open the Jandex index resource caused an exception. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The attempt to read the Jandex index failed with an exception. |
Action | For more information, see the exception and the associated FFDC message. |
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 shows the proportion of a module which was scanned for annotations using Jandex indexes. Module locations are either the module itself, or, for a Web module, are the WEB-INF/classes folder and WEB-INF/lib Jar files of the module. |
Action | No action is required if Jandex indexes are intended to be read for the application. To ignore Jandex indexes for a single application, then set the useJandex="false" attribute in the 'application' element of that application in server.xml. Alternatively, to ignore Jandex indexes in all applications, set useJandex="false" in the 'applicationManger' element in server.xml. |
Explanation | This shows the proportion of a module which was scanned for annotations using Jandex indexes. Module locations are either the module itself, or, for a Web module, are the WEB-INF/classes folder and WEB-INF/lib Jar files of the module. |
Action | No action is required if Jandex indexes are intended to be read for the application. To ignore Jandex indexes for a single application, then set the useJandex="false" attribute in the 'application' element of that application in server.xml. Alternatively, to ignore Jandex indexes in all applications, set useJandex="false" in the 'applicationManger' element in server.xml. |
Explanation | An exception occured while accessing annotations cache data. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The class and annotations data could not be scanned. The associated module may function incorrectly. |
Action | For more information, see the exception and the associated FFDC message. |
Explanation | The directory and name of a ".class" resource do not match the the name of the class which is recorded within the ".class" resource. The class resource will be ignored. |
Action | Move the class resource to the directory which matches the class's qualified name. Rename the class resource to match the class's qualified name. |
Explanation | The application could not be converted to a thin application. The application will continue to run from the original JAR. |
Action | Attempt to resolve the issue in the exception message and either restart the server or update the application. |
Explanation | The currently configured Spring Boot feature is not compatible with application content. |
Action | Configure a version of the Spring Boot feature that is compatible with application content. |
Explanation | The currently configured Spring Boot feature is not compatible with application content. |
Action | Configure a version of the Spring Boot feature that is compatible with application content. |
Explanation | The application uses Servlets but no Servlet feature is configured. |
Action | Configure one of the specified Servlet features. |
Explanation | Configuring multiple Spring Boot applications in the same server configuration is not supported. |
Action | Configure only one Spring Boot application per server configuration. |
Explanation | Spring Boot applications must contain a META-INF/MANIFEST.MF file. |
Action | Configure a valid Spring Boot application, which contains a META-INF/MANIFEST.MF file, with the server. |
Explanation | Spring Boot applications must contain a main class specified by the Start-Class manifest header. |
Action | Configure a valid Spring Boot application, which contains a Start-Class manifest header, with the server. |
Explanation | The application is a secure application, and it requires an SSL feature to be configured in the server.xml file. |
Action | Configure the transportSecurity-1.0 feature in the server.xml file. |
Explanation | The application uses Web Sockets but no Web Socket feature is configured. |
Action | Configure one of the specified Web Socket features. |
Explanation | Compression is not supported and the setting will be ignored, but the application will continue to function otherwise. |
Action | No user action is necessary. |
Explanation | Session timeout and session persistence must be configured in the server.xml file. These application session settings will be ignored. |
Action | Configure session timeout and session persistence in the server.xml file. |
Explanation | A Spring Boot version has been detected that is not supported by the server. |
Action | Update the Spring Boot application to use a version of Spring Boot that is within the required version range. |
Explanation | The application did not issue the starting event in the expected time. The server might be overloaded or the application might be large. If the application is starting as part of server startup, the sever startup can finish without waiting for the application to start. |
Action | If the application eventually starts, then no action is required. If the application does not start, check the server logs to see whether other messages indicate a cause. |
Explanation | The packaged Liberty server JAR file is missing a Server-Name manifest header, entries for the server root, or entries for the lib.index.cache directory. |
Action | Configure a valid packaged Liberty server JAR file. |
Explanation | Spring Boot has specific Java version requirements. The current Java version does not support the application Spring Boot version. |
Action | Either, change the Java version to a required version, or rebuild the application using a different Spring Boot version. |
Explanation | The packaged Liberty Server JAR file must contain a configured Spring Boot application. |
Action | Configure a valid packaged Liberty server JAR file. |
Explanation | The currently configured Spring Boot feature is not compatible with application content. |
Action | Configure a version of the Spring Boot feature that is compatible with application content. |
Explanation | The application uses Servlets but a no Servlet feature is configured. |
Action | Configure the specified Servlet feature. |
Explanation | The application uses Web Sockets but no Web Socket feature is configured. |
Action | Configure the specified Web Socket feature. |
Explanation | A checkpoint was requested. The server stopped and its current state is written to disk. |
Action | Check the documentation for details of the checkpoint and restore operations. |
Explanation | A restore operation was run on a Liberty server checkpoint image. |
Action | Check the documentation for details of the checkpoint and restore operations. |
Explanation | A checkpoint request for the server has failed. A valid checkpoint process image for the server has not been created. |
Action | Inspect the checkpoint directory located in the server logs directory for additional log files to determine why the checkpoint failed. |
Explanation | An attempt to restore the server from a checkpoint failed. The server is not running. |
Action | Inspect the checkpoint directory located in the server logs directory for additional log files to determine why the server could not be restored. |
Explanation | An unexpected error occurred during a checkpoint request or during an attempt to restore the server from a checkpoint. |
Action | Inspect the checkpoint directory located in the server logs directory for additional log files to determine why the error occurred. |
Explanation | The server checkpoint action can only be used with features that support checkpoint. |
Action | Only enable features that support checkpoint to use a server checkpoint action. Check the documentation for details on the features that support checkpoint. |
Explanation | An exception occurred while preparing to take a checkpoint. |
Action | Inspect the server logs directory for additional log files to determine why the server checkpoint failed. |
Explanation | An exception occurred while restoring the server process. |
Action | Inspect the server logs directory for additional log files to determine why the server failed to restore. |
Explanation | The server checkpoint action can only be used with a Java version that supports checkpoint. |
Action | Use a Java version that supports checkpoint. Check the documentation for details on the required Java version that supports checkpoint. |
Explanation | The configuration value was accessed during a checkpoint action and updated before the server process got restored. Depending on how the application accesses the configuration, the updated value might not be used. |
Action | Avoid accessing configuration properties during checkpoint. |
Explanation | An unrecognized property is configured on a context service. |
Action | Remove or correct the unrecognized property. |
Explanation | The application server is unable to find provider(s) of the specified type(s) of thread context. |
Action | Ensure the provider(s) of the requested thread context are enabled. |
Explanation | At most, one element of each type of context provider may be configured under a context service. |
Action | Remove duplicate context provider elements from the context service configuration. |
Explanation | In order to be serialized, a context service must have a unique id attribute or jndiName attribute. |
Action | Add an id attribute or jndiName attribute to the context service configuration. |
Explanation | The application server is unable to find a provider of the specified type of thread context. |
Action | Ensure that the feature which provides the specified type of thread context is enabled. |
Explanation | A context service with the specified id or jndiName is not found in the configuration. |
Action | Ensure that a context service with the specified id or jndiName exists in the configuration and is valid. |
Explanation | The application that submitted a task must be available in order for the task to start. |
Action | Ensure the application is started and resubmit the task. |
Explanation | The module that submitted a task must be available in order for the task to start. |
Action | Ensure the module is started and resubmit the task. |
Explanation | The application component that submitted a task must be available in order for the task to start. |
Action | Ensure the application component is started and resubmit the task. |
Explanation | An infinite chain of dependencies exists because baseContextRef directly or indirectly points back to the same context service instance. |
Action | Update the context service configuration to break the infinite chain of dependencies. |
Explanation | A resource might become unavailable due to the server shutting down or because of a configuration change, either to itself or another service upon which it depends. |
Action | Verify the configuration of the resource and any resources upon which it depends. |
Explanation | A task submitted to an executor has failed. Refer to the exception message for the cause. |
Action | Correct the cause of the failure and resubmit the task. |
Explanation | A managed task listener operation has failed. Refer to the exception message for the cause. |
Action | Correct the cause of the failure and decide whether or not to resubmit the task. |
Explanation | The skipRun operation for the Trigger has failed, causing the current execution attempt for the task to be skipped. |
Action | Correct the cause of the failure and decide whether or not to resubmit the task. |
Explanation | Execution of the task has been canceled. |
Action | No action is required. |
Explanation | The task cannot be submitted because it is not valid. |
Action | Update the application to submit a valid task to the ExecutorService. |
Explanation | All of the tasks were canceled before any task could be invoked. |
Action | No action is required. |
Explanation | The ManagedTaskListener taskSubmitted and taskStarting methods run on the thread that will submit or start the task. Therefore, the Future supplied to these methods must not be used to wait for the task. |
Action | Update the application to avoid invoking get on the Future that is supplied to taskSubmitted and taskStarting. |
Explanation | Some execution property values are not valid for managed executors, but might be valid for other resource types such as context service or managed thread factory. |
Action | Update the application to omit the execution property or set it to a valid value. |
Explanation | The MicroProfile Context Propagation specification permits no more than one ThreadContextProvider for each context type. |
Action | Update the available application, libraries, or both so that no more than one ThreadContextProvider of the specified type exists. |
Explanation | A thread context type can be configured in no more than one category when building or injecting a ManagedExecutor. |
Action | Review and correct the categorization of thread context types in your ManagedExecutor builder or ManagedExecutorConfig annotation. |
Explanation | A thread context type can be configured in no more than one category when building or injecting a ThreadContext instance. |
Action | Review and correct the categorization of thread context types in your ThreadContext builder or ThreadContextConfig annotation. |
Explanation | For each configured thread context type that is not provided by the server, a thread context provider must be available on the application's thread context class loader. Thread context types provided by the server include: Application, CDI, Security, Transaction. |
Action | Update the application, libraries or both to include a thread context provider for each configured thread context type that is not provided by the server. Alternatively, update the application to only use the context types that are available. |
Explanation | The managed executor implementation of CompletableFuture does not provide static method equivalents to the static methods of CompletableFuture. |
Action | Update the application to use the method that is recommended in the message in place of the requested operation. |
Explanation | A ManagedExecutor or ThreadContext that is configured to propagate transaction contexts can propagate empty transaction contexts only. Therefore, you cannot create contextual actions and tasks within a transaction. |
Action | Create the contextual action or task outside of a transaction. Alternatively, configure the ManagedExecutor or ThreadContext to not propagate transaction contexts. |
Explanation | When CDI context is captured, only CDI beans that have been accessed at that point in time have been created by the CDI runtime. As a result, CDI beans that are first accessed in contextual operations cannot propagate their state correctly to subsequent contextual operations. |
Action | The application must be changed to invoke some CDI bean operation, such as a public method, before context for the operation is captured. |
Explanation | Too much load on the system to process resource definition annotations and deployment descriptor entries before the application attempts to use them. |
Action | View the messages.log file to identify the occurrence of an error. Otherwise, reduce the load on the system. |
Explanation | The specified resource that implements the ContextService interface was inaccessible or not available because of any of the following reasons. 1.) A resource definition annotation or a resource definition in a deployment descriptor of the application specifies an incorrect JNDI name at which to find the resource that implements the ContextService interface. 2.) The resource that implements the ContextService interface is defined in a scope that is not accessible to the resource that requires the resource that implements the ContextService interface. 3.) The system is under too much load to register a resource that implements the ContextService interface in a timely manner. |
Action | Correct the application to refer to the JNDI name of the ContextService that is accessible. If the specified JNDI name is correct, reduce the load on the system. |
Explanation | A thread context type can be configured in any one of the cleared, propagated, or unchanged context type categories. The context type cannot be configured in multiple context type categories. |
Action | Correct the configuration to specify the thread context type in at most one category. |
Explanation | There can only be one thread context provider for each context type. |
Action | Update the application, libraries, or both so that no more than one thread context provider of the specified context type is accessible to the application. |
Explanation | Third-party thread context types are not compatible with serialization and cannot be configured to be propagated for serializable contextual proxies. |
Action | Update the application to request a non-serializable contextual proxy or ensure that no third-party context types are configured to be propagated. |
Explanation | The Jakarta concurrency specification limits the range of valid return types for methods that have this annotation. |
Action | Update the method within the application to switch to one of the supported return types, or remove the annotation from the method. |
Explanation | This annotation must not be specified at the class level. |
Action | Move the annotation to the individual methods of the class. |
Explanation | The JNDI name must resolve to a resource that implements the ManagedExecutorService interface or ManagedScheduledExecutorService interface. |
Action | Correct the JNDI name to specify a resource that is accessible to the application component and implements the ManagedExecutorService interface or ManagedScheduledExecutorService interface. |
Explanation | The use of two annotations together depends on whether the value of the first annotation that is specified is permitted with the second annotation. |
Action | Update the application to switch to one of the supported values or remove one of the annotations. |
Explanation | Task execution was marked to roll back. The task will retry after the specified number of seconds. |
Action | Wait for the task to retry. |
Explanation | Task execution failed and rolled back. The task will retry after the specified number of seconds. |
Action | If the failure is transient, wait for the task to retry. Otherwise, correct the cause of the failure if the failure is unexpected. |
Explanation | Task execution was marked to roll back. |
Action | If the rollback is unexpected, reschedule the task. |
Explanation | Task execution failed and rolled back. |
Action | Correct the cause of the failure, if the failure is unexpected, and reschedule the task. |
Explanation | The task took too long to run, so the transaction is being rolled back. |
Action | A larger transaction timeout might be needed, or the task might need to be made shorter. |
Explanation | The task took too long to run, so the transaction is being rolled back. |
Action | A larger missedTaskThreshold might be needed, or the task might need to be made shorter. |
Explanation | The application marked the transaction to roll back with setRollbackOnly, or an error or timeout caused the rollback. |
Action | If the rollback is unexpected, check the logs and the application. |
Explanation | The task has reached the limit of consecutive retries and will not be attempted again. |
Action | If the rollbacks or failures are unexpected, determine the cause and reschedule the task. If the rollbacks and failures are intermittent, consider increasing the retry limit. |
Explanation | The task has reached the limit of consecutive retries and will not be attempted again. |
Action | If the failures or rollbacks are unexpected, determine the cause and reschedule the task. If the rollbacks and failures are intermittent, consider increasing the retry limit. |
Explanation | A value that is outside of the allowed range is configured for the specified property. |
Action | Configure a value within the allowed range. |
Explanation | The specified configuration attributes are not compatible. |
Action | Update the configuration to remove one of the configuration attributes. |
Explanation | Schedule persistent tasks only from a thread that is associated with an application or feature with a serializable class loader identity. |
Action | Ensure that context for the application or feature is present on the thread when scheduling tasks. |
Explanation | TaskStatus is an immutable snapshot of task state. Any value returned from isDone or isCancelled prior to the task ending would become invalid once the task ends. An error is raised when attempted before the task ends to avoid returning an unreliable value. |
Action | Use the getNextExecutionTime method to determine if a task has ended. Use the isDone and isCancelled methods only if the task has ended. |
Explanation | TaskStatus is an immutable snapshot of task state. Any value returned from get prior to the task ending would become invalid once another execution attempt completes or the task ends. An error is raised when attempted before the task ends to avoid returning an unreliable value. |
Action | Use the getResult method to obtain the result of the execution attempt that was the most recent attempt when the TaskStatus instance was obtained. |
Explanation | TaskStatus is an immutable snapshot of task state. Any value returned from getDelay prior to the task ending would become invalid once another execution attempt completes. An error is raised when attempted before the task ends to avoid returning an unreliable value. |
Action | Use the getNextExecutionTime method to get the expected next execution time that corresponds to the time when the TaskStatus was obtained. |
Explanation | An error occurred which prevented the task result from being obtained. |
Action | Refer to the cause exception to correct the problem, then reschedule the task. |
Explanation | The task failed to run due to the specified exception. |
Action | Refer to the cause exception to correct the problem, then reschedule the task. |
Explanation | The task has reached the limit of consecutive retries and will not be attempted again. |
Action | Refer to the cause exception to correct the problem, then reschedule the task. If the problem is intermittent, consider increasing the retry limit. |
Explanation | The application and module that scheduled a task must be available so that the task can run. |
Action | Ensure the application and the module that scheduled the task are available. Alternately, cancel the task if it is no longer needed. |
Explanation | An error occurred while attempting to perform the requested operation. |
Action | Check the server logs for details about the operation error. |
Explanation | The waitForAll and waitForAny methods require a work item list. |
Action | Provide a list of work items to the waitForAll or the waitForAny method. |
Explanation | The waitForAll and waitForAny methods require a positive (or zero) timeout value. |
Action | Specify a non-negative timeout value for the waitForAll or waitForAny method. |
Explanation | Work and WorkListener implementations cannot also implement EnterpriseBean. |
Action | Use a remote or local interface to the Enterprise Java Bean (EJB). |
Explanation | All of the items in the work item collection must implement the commonj.work.WorkItem interface. |
Action | Replace the item with a commonj.work.WorkItem or remove it from the collection before invoking the waitForAll or waitForAny methods. |
Explanation | The schedule methods of WorkManager require a valid commonj.work.Work instance to schedule. |
Action | Provide a non-null commonj.work.Work implementation when invoking schedule. |
Explanation | WorkListener.workAccepted, WorkListener.workStarted, and Work.run implementations must not invoke the waitForAll method on the work item that represents the completion of the same Work.run implementation. |
Action | When waiting for work items from WorkListener.workAccepted, WorkListener.workStarted, and Work.run, avoid including the work item for the same work in the list of work items to wait for. |
Explanation | The work item did not start because an error prevented context from being established on the thread. |
Action | No action is needed if the server is shutting down. |
Explanation | After the work item completed, an error prevented context from being restored on the thread. |
Action | No action is needed if the server is shutting down. |
Explanation | The user-defined WorkListener implementation of the workRejected, workAccepted, workStarted, or workCompleted method raised an undeclared error or exception. |
Action | Fix the error in the WorkListener implementation. |
Explanation | The requested operation cannot run because the TimerManager is stopped. |
Action | If the server is shutting down or undergoing a configuration update or the application is stopping, then no action is needed. Otherwise, obtain a new TimerManager instance. |
Explanation | The CommonJ TimerManager API does not permit a null TimerListener to be supplied to the schedule and scheduleAtFixedRate methods. |
Action | Invoke the TimerManager schedule or scheduleAtFixedRate method with a non-null TimerListener. |
Explanation | The CommonJ TimerManager API does not permit a null date to be supplied to the schedule and scheduleAtFixedRate methods. |
Action | Invoke the TimerManager schedule or scheduleAtFixedRate method with a non-null date. |
Explanation | The CommonJ TimerManager API does not permit a negative initial delay to be supplied to the schedule and scheduleAtFixedRate methods. |
Action | Invoke the TimerManager schedule or scheduleAtFixedRate method with an initial delay value that is positive or 0. |
Explanation | The CommonJ TimerManager API does not permit a negative period to be supplied to the schedule and scheduleAtFixedRate methods. |
Action | Invoke the TimerManager schedule or scheduleAtFixedRate method with a period value that is positive. |
Explanation | The specified TimerListener method failed with an error. |
Action | Fix the error in the TimerListener implementation. |
Explanation | A required attribute is missing from the specified element. |
Action | Correct the deployment descriptor by adding the missing attribute. |
Explanation | The root element of the deployment descriptor is incorrect. |
Action | Correct the root element of the deployment descriptor. |
Explanation | The root element was missing from the deployment descriptor. |
Action | Correct the deployment descriptor. |
Explanation | The deployment descriptor doesn't appear to be proper xml. |
Action | Correct the deployment descriptor. |
Explanation | The namespace of the elements and attributes in the deployment descriptor were not consistent. |
Action | Correct the deployment descriptor. |
Explanation | An attribute not defined to be in the deployment descriptor was encountered. |
Action | Correct the deployment descriptor. |
Explanation | Text content not defined to be in the deployment descriptor was encountered. |
Action | Correct the deployment descriptor. |
Explanation | The namespace of the elements and attributes in the deployment descriptor were not consistent. |
Action | Correct the deployment descriptor. |
Explanation | An element not defined to be in the deployment descriptor was encountered. |
Action | Correct the deployment descriptor. |
Explanation | The prefix of the HREF value specifies a path to a referenced deployment descriptor. The prefix does not match the path of that referenced deployment descriptor. |
Action | Correct the HREF value. |
Explanation | The version which was specified in the deployment descriptor is not valid for that type of deployment descriptor. |
Action | Correct the version specified in the deployment descriptor. |
Explanation | The namespace which was specified in the deployment descriptor is not valid for that type of deployment descriptor. |
Action | Correct the namespace specified in the deployment descriptor. |
Explanation | The version which was specified for the deployment descriptor is not supported by the features provisioned by the server configuration. |
Action | Update the server configuration to provision features which support the version. |
Explanation | The deployment descriptor is required to have the specified namespace. |
Action | Add the required namespace to the deployment descriptor. |
Explanation | The version was not specified in the root element of the deployment descriptor. |
Action | Verify and correct the version in the root element of the deployment descriptor. |
Explanation | Some elements in the deployment descriptor are only permitted to appear once if present. |
Action | Correct the deployment descriptor. |
Explanation | A required child element is missing from the specified parent element. |
Action | Correct the deployment descriptor by adding the required child element. |
Explanation | The <specified-identity> child element is missing for the <run-as-mode> element which has the mode set to SPECIFIED_IDENTITY. |
Action | Correct the deployment descriptor by adding the required child element or change the mode. |
Explanation | All session and message-driven bean names must be unique. The specified bean name is used more than once. |
Action | Correct the deployment descriptor by renaming any duplicate enterprise bean names. |
Explanation | The value of the specified attribute must be unique across all elements of the same type. |
Action | Correct the deployment descriptor by renaming any duplicate attribute values. |
Explanation | The validation configuration file does not match the validation configuration schemas (validation-configuration-1.0.xsd and validation-configuration-1.1.xsd). Either the configuration file was not intended for use for bean validation, or the configuration file is malformed. The configuration file is being ignored. The BeanValidationService will not create a ValidatorFactory. |
Action | If the validation configuration file is not intended for bean validation, the warning message can be ignored. If the validation configuration file is intended for bean validation, do not ignore the warning message. The bean validation service is not running as intended. To diagnose the problem, enable bean validation runtime trace, stop and restart the server, and examine trace output for unexpected exceptions relating to bean validation. For example, "Unexpected exception when trying to unmarshall the validation.xml file." Examine the exception stack trace for debugging assistance. |
Explanation | An error occurred while parsing the XML deployment descriptor. Refer to the error message for further explanation. |
Action | Correct the deployment descriptor to remove the error. |
Explanation | The deployment descriptor specifies a value that is not valid. |
Action | Correct the deployment descriptor to use one of the expected values. |
Explanation | The deployment descriptor specifies a value that is not a number in the range -2147483648 to 2147483647. |
Action | Correct the deployment descriptor to use a valid integer number. |
Explanation | The deployment descriptor specifies a value that is not a number in the range -9223372036854775808 to 9223372036854775807. |
Action | Correct the deployment descriptor to use a valid long number. |
Explanation | Bindings and extension configuration elements must have a ''moduleName'' attribute. |
Action | Ensure that a ''moduleName'' attribute is present in all bindings and extension configuration elements. |
Explanation | The ''moduleName' attributes of bindings and extension configuration elements must match application module names. |
Action | Ensure that all ''moduleName' attributes of bindings and extension configuration elements match application module names. |
Explanation | The ''moduleName' attributes of bindings and extension configuration elements may not be duplicated. |
Action | Ensure that all ''moduleName' attributes of bindings and extension configuration elements are unique. |
Explanation | The element value is not a valid HREF value: The value must have a ''#'' character and the ''#'' character must not be the first or last character of the value. |
Action | Correct the HREF value. |
Explanation | The type of the object which is referenced by the HREF value is incorrect. |
Action | Correct the HREF value. |
Explanation | The HREF ID does not resolve to any available element of the referenced deployment descriptor. The HREF ID must match the ID of an element of the referenced deployment descriptor. |
Action | Correct either the HREF ID in the referencing deployment descriptor or the ID value in the referenced deployment descriptor. |
Explanation | The element is required to provide an HREF attribute. An HREF attribute has name ''href''. |
Action | Add an HREF attribute to the element. |
Explanation | The class must have a no-arguments constructor and must implement the javax.security.auth.callback.CallbackHandler interface. |
Action | Add a no-arguments constructor to the callback handler class. |
Explanation | An exception occurs when the container invokes the PostConstruct method. |
Action | Ensure that the PostConstruct method is defined correctly in the deployment descriptor or annotated correctly in the class. |
Explanation | An exception occurs when the container invokes the PreDestroy method. |
Action | Ensure that the PreDestroy method is defined correctly in the deployment descriptor or annotated correctly in the class. |
Explanation | There is more than one PostConstruct method or PreDestroy method declared in the class. |
Action | No action is required. The container invokes the first method that it detects. |