WebSphere Process Server messages     Operating Systems: All supported

CWMDF

CWMDF0001E: Component {0} already exists.
Problem Component names must be unique.
User response This error indicates a severe error condition internal to WebSphere. Report this problem to WebSphere Support.
CWMDF0002E: Annotation processing failed with the following error: {0}
Problem Processing of annotations failed. Possibly the ear, jar, or war was not packaged properly.
User response See exception or error message for possible action.
CWMDF0003E: The {0} business interface class cannot be both remote and local.
Problem A business interfaces cannot be defined within XML or annotations as both remote and local.
User response Determine if business interface should be remote or local and fix the annotations or XML.
CWMDF0004E: Bean class {0} must not contain both @Local and @Remote annotations, each with no parameters
Problem If both @Remote and @Local annotations are put on a bean class, one or the other must specify the business interface as a parameter.
User response Add the name of the business interface to eithe the @Remote or @Local annotations.
CWMDF0005E: The implements clause on Bean class {0} contains multiple interfaces and the bean class has a @Remote or @Local annotation contains no parameters.
Problem You can only define one business interface on the implements clause of a bean class if the @Remote or @Local annotation has no parameters.
User response 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.
CWMDF0006E: Session bean "{0}" has been defined as "{1}" in XML and "{2}" in annotations.
Problem 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.
User response 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.
CWMDF0007E: Ear {0} failed to open with the following exception: {1}.
Problem Ear file failed to open. Possibly the ear file was not packaged properly.
User response See exception or error message and fix ear file.
CWMDF0008W: Class {0} failed to load with the following exception: {1}.
Problem Class failed to load. Possibly the class depends on a class that is not within the scope of the ArchiveClassLoader.
User response See exception or error message. Possibly add missing jar file to MANIFEST classpath.
CWMDF0009W: Methods of class {0} failed to load with the following exception: {1}.
Problem 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.
User response See exception or error message. Possibly add missing jar file to MANIFEST classpath.
CWMDF0011E: @MessageDrivenAnnotation has an @AnnotationConfigProperty sub-annotation with a duplicate property: {0}.
Problem All properties on the @ActivationConfigProperty annotations must be unique.
User response Check the @MessageDrivenAnnotation and remove or change duplicate property name on @ActivationConfigProperty sub-annotation.
CWMDF0012E: The bean class {0} for EJB {1} is not found.
Problem A bean class that has been defined in XML for an EJB cannot be found in the ear.
User response Check the XML for EJB {1} and ensure that the ejb class specified exists within the ear.
CWMDF0013E: The {0} Enterprise JavaBeans (EJB) class name, which is defined in XML for the {1} EJB file, is not correct..
Problem The EJB class name must exist in the file system.
User response Check the XML for the {1} EJB file and ensure that the specified EJB class exists within the file system.
CWMDF0014E: The {0} bean has been defined as the {1} transaction management type in XML and the {2} transaction management type in annotations..
Problem Do not define an EJB to use both CONTAINER and BEAN-managed transactions.
User response 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.
CWMDF0015E: The class loader cannot load the {0} interface on the {1} Enterprise JavaBeans (EJB) file..
Problem 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.
User response Ensure that the jar file containing "{0}" is either contained in a defined library directory for this EJB or specified in the manifest classpath for this EJB jar file.
CWMDF0016I: This message is an English-only Informational message: {0}.
Problem This informational message is not translated.
User response See message for details.
CWMDF0017W: This message is an English-only Warning message: {0}.
Problem This warning message is not translated.
User response See message for details.
CWMDF0018E: This message is an English-only Error message: {0}.
Problem This error message is not translated.
User response See message for details.
CWMDF0019E: The product does not support container-managed persistence (CMP) Entity beans in Enterprise JavaBeans (EJB) 3.0-level modules. The {0} bean in the {1} module must be moved to an EJB 2.1 or earlier-level module.
Problem CMP Entity beans are supported by the product in EJB 2.1 or earlier-level modules only.
User response Package all CMP Entity beans in EJB 2.1 or earlier-level modules and then reinstall the application.
CWMDF0022W: An attempt to scan class file "{0}" in JAR file "{1}" failed with exception: "{2}".
Problem An attempt to byte-code scan a class file for Java annotations has failed. It is likely that the class file is corrupted.
User response Ensure that the class file is not corrupted.
CWMDF0023W: An attempt to scan a class file in the directory "{0}" failed with exception: "{1}".
Problem An attempt to byte-code scan a class file for Java annotations has failed. It is likely that a class file is corrupted.
User response Ensure that the class files in the specified directory are not corrupted.
CWMDF0024W: An attempt to scan class file "{0}" in module "{1}" failed with exception: "{2}".
Problem An attempt to byte-code scan a class file for Java annotations has failed. It is likely that the class file is corrupted.
User response Ensure that the class file is not corrupted.
CWMDF9000E: Error: Unexpected exception "{0}" occurred.
Problem An unexpected exception occured during command processing.
User response Add the -verbose option to see more information.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.metadata.metadata.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)