Explanation | The server is starting the EJB module. |
Action | No action is required. |
Explanation | The server has started the EJB module. |
Action | No action is required. |
Explanation | The server was unable to start the EJB module. |
Action | Use the exception information to identify the source of the issue, and to resolve the problem. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The server is stopping the EJB module. |
Action | No action is required. |
Explanation | The server has stopped the EJB module. |
Action | No action is required. |
Explanation | The server was unable to stop the EJB module. |
Action | Use the exception information to identify the source of the issue, and to resolve the problem. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The enterprise bean was configured to start when it was first used rather than when its module is started. The enterprise bean failed to start when it was first used. |
Action | Use the exception information to identify the source of the issue, and to resolve the problem. See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An error occurred creating an instance of the enterprise bean with the specified JNDI name. |
Action | See the nested exception or a prior error for more information about the error. |
Explanation | The Liberty profile does not support enterprise bean home or component interfaces. Only business interfaces are supported in the Liberty profile. |
Action | Modify the application to remove the use of enterprise bean home and component interfaces. |
Explanation | The Liberty profile does not support enterprise bean remote interfaces. Only local interfaces are supported in the Liberty profile. |
Action | Modify the application to remove the use of enterprise bean remote interfaces. |
Explanation | Automatic enterprise bean timers declared in either a deployment descriptor or annotation are not supported in the Liberty profile and will be ignored during run time. Depending on the intended use of the enterprise bean timers by the application, the application may or may not run as expected. |
Action | Remove the use of unsupported automatic timers from the application. |
Explanation | The Liberty profile does not support enterprise bean home or component interfaces. Only business interfaces are supported in the Liberty profile. |
Action | Modify the application to remove the use of enterprise bean home and component interfaces. |
Explanation | The Liberty profile does not support enterprise bean remote interfaces. Only local interfaces are supported in the Liberty profile. |
Action | Modify the application to remove the use of enterprise bean remote interfaces. |
Explanation | Multiple enterprise beans were defined with the same name in the ejb-jar.xml file. Each enterprise bean must have a unique name. |
Action | Remove the duplicate enterprise bean definitions. |
Explanation | The <ejb-class> element was not specified in the ejb-jar.xml file. This element is required for enterprise beans defined without using an annotation. |
Action | Add the <ejb-class> element to the enterprise bean definition in the ejb-jar.xml file. |
Explanation | The <session-type> element was not specified in the ejb-jar.xml file. This element is required for session beans defined without using an annotation. |
Action | Add the <session-type> element to the session bean definition. |
Explanation | An enterprise bean can only have one type, but incompatible types were specified in the ejb-jar.xml file and by the annotation. |
Action | Change the element type or the annotation type for the enterprise bean. |
Explanation | An enterprise bean can only have one type, but multiple component-defining annotations were specified. |
Action | Remove one of the component-defining annotations. |
Explanation | An enterprise bean can only have one type, but incompatible types were specified in the ejb-jar.xml file and by the annotation. |
Action | Change the element type or the annotation type for the enterprise bean. |
Explanation | An enterprise bean can only be declared with one class, but it was declared with different classes by annotations on two separate classes. |
Action | Remove one of the annotations, or change one of the enterprise bean names. |
Explanation | Specifying the @Remote or @Local annotation without a value indicates that the business interface on the implements clause should be considered remote or local respectively, so both annotations cannot be specified without a value. |
Action | Remove the annotation, or specify the annotations with the business interfaces. |
Explanation | Specifying the @Remote or @Local annotation without a value indicates that the business interface on the implements clause should be considered remote or local respectively, but the class has no business interfaces on its implements clause. |
Action | Add a business interface to the implements clause, remove the annotation, or specify the annotation with the business interfaces. |
Explanation | Specifying the @Remote or @Local annotation without a value indicates that the business interface on the implements clause should be considered remote or local respectively, but the class has multiple business interfaces on its implements clause. |
Action | Remove all but one business interface on the implements clause, or specify the annotation with all the business interfaces. |
Explanation | A class can be specified for an enterprise bean as either a local business interface or a remote business interface but not both. |
Action | Update the enterprise bean class, the interface class, or the deployment descriptor so that the interface is specified as either a local business interface or a remote business interface but not both. |
Explanation | The @Remote and @Local annotations can only have a value when they are specified on an enterprise bean class. |
Action | Remove the value from the @Remote or @Local annotation on the interface. |
Explanation | The enterprise bean name might be incorrect, or an extension might have been specified for an enterprise bean that does not exist. |
Action | Correct the enterprise bean name in the ibm-ejb-jar-ext.xml file. |
Explanation | The boundary attribute value ACTIVITY_SESSION of the <local-transaction> extension is not supported in the Liberty profile. |
Action | Update the ibm-ejb-jar-ext.xml file to specify BEAN_METHOD for the boundary, or remove the boundary attribute to use the default, which is BEAN_METHOD. |
Explanation | An enterprise bean can only be defined with one class, but it was declared with different classes in XML and by an annotation. |
Action | Remove the class from ejb-jar.xml, remove the annotation, or change one of the enterprise bean names. |