Explanation | Component names must be unique. |
Action | This error indicates a severe error condition internal to WebSphere. Report this problem to WebSphere Support. |
Explanation | Processing of annotations failed. Possibly the ear, jar, or war was not packaged properly. |
Action | See exception or error message for possible action. |
Explanation | A business interfaces cannot be defined within XML or annotations as both remote and local. |
Action | Determine if business interface should be remote or local and fix the annotations or XML. |
Explanation | If both @Remote and @Local annotations are put on a bean class, one or the other must specify the business interface as a parameter. |
Action | Add the name of the business interface to eithe the @Remote or @Local annotations. |
Explanation | You can only define one business interface on the implements clause of a bean class if the @Remote or @Local annotation has no parameters. |
Action | Ensure the implements clause of the bean class contains only one business interface or change the @Remote or @Local annotation to list the business interfaces as parameters. |
Explanation | A session bean must not be defined to be both stateful and stateless. For example: a session bean cannot contain a @Stateless annotation and be defined with a Session type of stateful in XML. |
Action | Check the source code annotation and ejb-jar.xml configuration settings for this bean. Ensure that the session type defined in XML matches the type defined in annotations or remove the @Stateful or @Stateless annotation. |
Explanation | Ear file failed to open. Possibly the ear file was not packaged properly. |
Action | See exception or error message and fix ear file. |
Explanation | Class failed to load. Possibly the class depends on a class that is not within the scope of the ArchiveClassLoader. |
Action | See exception or error message. Possibly add missing jar file to the Class-Path within the Manifest.mf file. |
Explanation | Methods failed to load for class {0}. Possibly the class contains a method whose signature or parameters are not within the scope of the ArchiveClassloader. |
Action | See exception or error message. Possibly add missing jar file to the Class-Path within the Manifest.mf file. |
Explanation | All properties on the @ActivationConfigProperty annotations must be unique. |
Action | Check the @MessageDrivenAnnotation and remove or change duplicate property name on @ActivationConfigProperty sub-annotation. |
Explanation | A bean class that has been defined in XML for an EJB cannot be found in the ear. |
Action | Check the XML for EJB {1} and ensure that the ejb class specified exists within the ear. |
Explanation | The EJB class name must exist in the file system. |
Action | Check the XML for the {1} EJB file and ensure that the specified EJB class exists within the file system. |
Explanation | Do not define an EJB to use both CONTAINER and BEAN-managed transactions. |
Action | Check the @TransactionManagement annotation and ejb-jar.xml configuration settings for this bean. Ensure that the transaction management type that is defined in XML matches the type that is defined in the annotation or remove one of the two settings. |
Explanation | All interface classes must be in the same Java archive (JAR) file as the EJB file; inside a defined library directory; or in a JAR file that is specified in the manifest class path of the EJB jar file. |
Action | Ensure that the jar file containing "{0}" is either contained in a defined library directory for this EJB or specified in the Class-Path within the Manifest.mf file for this EJB jar file. |
Explanation | This informational message is not translated. |
Action | See message for details. |
Explanation | This warning message is not translated. |
Action | See message for details. |
Explanation | This error message is not translated. |
Action | See message for details. |
Explanation | CMP Entity beans are supported by the product in EJB 2.1 or earlier-level modules only. |
Action | Package all CMP Entity beans in EJB 2.1 or earlier-level modules and then reinstall the application. |
Explanation | An EJB must not be annotated with multiple ejb type annotations. For example: a session bean cannot contain a @Stateless annotation and @MessageDriven annotation. |
Action | Check the source code annotations for this bean. Remove any multiple ejb type annotations. |
Explanation | BMP Entity beans are supported by the product in EJB 2.1 or earlier-level modules only. |
Action | Package all BMP Entity beans in EJB 2.1 or earlier-level modules and then reinstall the application. |
Explanation | An attempt to byte-code scan a class file for Java annotations has failed. It is likely that the class file is corrupted. |
Action | Ensure that the class file is not corrupted. |
Explanation | An attempt to byte-code scan a class file for Java annotations has failed. It is likely that a class file is corrupted. |
Action | Ensure that the class files in the specified directory are not corrupted. |
Explanation | An attempt to byte-code scan a class file for Java annotations has failed. It is likely that the class file is corrupted. |
Action | Ensure that the class file is not corrupted. |
Explanation | An unexpected exception occured during command processing. |
Action | Add the -verbose option to see more information. |