Explanation | The close for the resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The close of the input stream for the resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | Opening an InputStream for the resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
Explanation | The close of the InputStream for the resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The file was being opened as a JarFile and that action caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
Explanation | An InputStream close for the resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
Explanation | The close of a class source caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | When the annotation scan process tried to open an input stream for the class, an exception occurred. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | When the annotation scan process tried to close an input stream for the class, an exception occurred. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The annotation scan process was creating a ClassReader to process the input stream for the resource, and that caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
Explanation | The close of the child class source caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The processing of class information read from an entry caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The close of the entry caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The processing of class information read from a file caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The close of the file caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The processing of class information read from a JAR entry caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The close of the file caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The processing of class information read from a resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The close of the resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
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 | See the exception and the associated FFDC message for more information. |
Explanation | The attempt to open the Jandex index resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The attempt to read the Jandex index failed with an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The attempt to open the Jandex index resource caused an exception. |
Action | See the exception and the associated FFDC message for more information. |
Explanation | The attempt to read the Jandex index failed with an exception. |
Action | 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 | 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 | 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 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 | 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 | A required attribute is missing from the specified element. |
Action | Correct the deployment descriptor by adding the missing attribute. |
Explanation | The root element is incorrect. |
Action | Validate the xml file to make sure the root element is correct. |
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 | An href attribute must start with the correct path to the descriptor being referenced. |
Action | Correct the deployment descriptor. |
Explanation | The version or the namespace were invalid or not specified in the root element of the deployment descriptor. |
Action | Verify and correct the version or namespace in the root element of the deployment descriptor. |
Explanation | Either the specified version and namespace are not valid, or the server configuration does not have a feature that can process the version and namespace. |
Action | Verify and correct the version or namespace in the root element of the deployment descriptor, or verify and correct the features in the server configuration. |
Explanation | An invalid version was specified in the root element of the deployment descriptor. |
Action | Verify and correct the version number in the root element of the deployment descriptor. |
Explanation | An invalid namespace was specified in the root element of the deployment descriptor. |
Action | Verify and correct the namespace in the root element of 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 BeanValidationService cannot create a ValidatorFactory because of an error parsing the validation.xml file with the validation-configuration-1.0.xsd schema file. This error may indicate that the validation.xml file is not intended for use by the Bean Validation run-time; therefore, this XML file is ignored. |
Action | If the validation.xml file is not for creating a ValidatorFactory instance, then ignore the message. However if the validation.xml file is intended to create a ValidatorFactory instance, then a problem exists. Enable Bean Validation run-time trace in the application server, stop the application, restart the application, and examine the trace output file for a trace event such as: 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 | The binding and extension configuration for EJB and web modules must contain a moduleName attribute that specifies the module to which the configuration applies. |
Action | Add a moduleName attribute to the web-bnd, web-ext, ejb-bnd, or ejb-ext element. |
Explanation | The binding and extension configuration for web modules must specify a valid moduleName attribute. At least one configuration has specified an invalid module name. The module name must be the name of the archive file that contains the web or EJB application. |
Action | Correct the moduleName attribute in the binding or extension configuration. |
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. |