WebSphere Process Server messages     Operating Systems: All supported

CWWJP

CWWJP0001E: The server cannot load the {1} Java Persistence API (JPA) provider in the {0} bundle, which is located in the {2} file. The following error occurred: {3}
Problem During server processing for the default JPA provider, the server cannot find the {2} file for the {1} provider in the {0} bundle. The following error occurred: {3}
User response Inspect the {0} JPA provider bundle to make sure that the following information exists: The META-INF/services/javax.persistence.spi.PersistenceProvider file defines the correct provider implementation class. The implementation class exists in the bundle. The provider Java archive (JAR) file is specified in the Bundle-ClassPath property in the META-INF/MANIFEST.MF file.
CWWJP0002E: The server cannot read the content of the {1} file in the {0} Java Persistence API (JPA) provider bundle. The following error occurred: {2}
Problem During server processing for the default JPA provider, the server cannot read the content of the {1} file in the {0} JPA provider bundle. The following error occurred: {2}
User response Inspect the {0} JPA provider bundle to make sure that the META-INF/services/javax.persistence.spi.PersistenceProvider file exists and is correctly formatted.
CWWJP0003E: The {0} extended persistence context can be initiated within the scope of a stateful session bean only.
Problem The Java Persistence API (JPA) specification requires that an extended persistence context be initiated within the scope of a stateful session bean only, and the application attempted to initiate the {0} extended persistence context within the scope of a different bean type.
User response Modify the application to initiate the extended persistence context within the scope of a stateful session bean, or change the persistence context.
CWWJP0004E: The server is unable to locate the {0} Java Persistence API (JPA) provider system default. The default JPA provider function is disabled.
Problem The Java Persistence API for WebSphere products provider is installed in the Application Server for the system default JPA provider. However, this default provider is not found. Therefore, the default JPA function is disabled.
User response Contact your system administrator to make a user-defined or the default system WSJPA implementation accessible to the application server.
CWWJP0005W: The {0} persistence unit in {1} module is using the {2} ClassLoader type. The Java Persistence API (JPA) entity function might not function as expected.
Problem To enable full JPA support, a persistence provider might need to inject code into a JPA entity. The {2} ClassLoader type does not support JPA code injection. Therefore, a JPA entity might not work as expected.
User response No action is required.
CWWJP0006I: The {0} class is loaded as the default Java Persistence API (JPA) provider.
Problem This message is for informational purposes only.
User response No action is required.
CWWJP0007W: The {0} persistence unit in the {2} module of the {1} application is already defined.
Problem As stated in Java Persistence API (JPA) specification section 6.2, the persistence unit name must be unique within a single Enterprise JavaBeans-Java archive (EJB-JAR) file, a Web archive (WAR) file, an application client JAR file, or an enterprise archive (EAR) file. The duplicate persistence unit will be ignored.
User response Before trying again, rename or remove the duplicate persistence unit.
CWWJP0008E: The server cannot locate the Java Transaction API (JTA) registry with a Java Naming Directory Interface (JNDI) lookup of the {0} name. The following error occurred: {1}
Problem The server runtime is not able to associate the operation thread with any Java Platform, Enterprise Edition 5 (Java EE 5) application component. This condition can occur when the JNDI client using the java: name is not executed on the thread of a server application request.
User response Make sure that a Java EE 5 application does not execute JNDI operations on java: names within static code blocks or in threads created by that Java EE 5 application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on java: names.
CWWJP0009E: The server cannot create an EntityManangerFactory factory for the {0} persistent unit from the {1} provider in {2} module.
Problem The {1} Java Persistence API (JPA) provider createContainerEntityManagerFactory method failed to return an EntityManagerFactory. This might occur if the incorrect JPA provider is used for the {0} persistent unit, or an error occurred in the {1} JPA provider.
User response Make sure the correct JPA provider has been configured for the persistent unit, and check for any previous errors from the JPA privider.
CWWJP0010W: The server cannot locate the deployed application, which is called {0}, when it attempts to find the {2} persistence unit in the {1} module.
Problem The {0} application is either not installed or has not been started.
User response Install or start the {0} application.
CWWJP0012E: The persistence unit name is not specified and a unique persistence unit is not found in the {0} application and {1} module.
Problem The application has defined a persistence unit or persistence context reference without a persistence unit name and a unique persistence unit cannot be found.
User response Change the application to specify a persistence unit name for the reference, or provide a unique persistence.
CWWJP0013E: The server cannot locate the {0} data source for the {1} persistence unit because it has encountered the following exception: {2}.
Problem The server has attempted to locate the {0} data source for the {1} persistence unit. However, a data source cannot be found.
User response Make sure that the requested data source is created and bound.
CWWJP0014E: An illegal format has been detected during the class transformation for the {0} class. The class has not been transformed.
Problem The Java Persistence API (JPA) provider has attempted to transform the {0} class and failed with an IllegalClassFormatException. Either the class file is corrupt or the JPA provider has a problem.
User response Correct the corrupt class file or contact the JPA provider for assistance.
CWWJP0015E: An error occurred in the {0} persistence provider when it attempted to create the container entity manager factory for the {1} persistence unit. The following error occurred: {2}
Problem The {0} Java Persistence API (JPA) provider createContainerEntityManagerFactory method failed with the following error: {2}
User response Contact the JPA provider for assistance.
CWWJP0016W: More than one <persistence-context-ref> with the {0} name are declared in the {1} deployment description file.
Problem More than one {0} persistence context reference is declared in the {1} deployment description file. All instances, except for the first instance, are ignored.
User response Before trying again, rename or remove the duplicate persistence context reference.
CWWJP0017I: The Java Persistence API (JPA) component has started.
Problem This message is for informational purposes only.
User response No action is required.
CWWJP0018E: Incorrect syntax or error detected in the {0} file. The following associated error message occurred: {1}
Problem The {0} file contains an error or errors and does not conform to the schema definition. The application might not function as expected.
User response Correct the error or errors in the persistence.xml file and try again.
CWWJP0019W: The {0} application has already started.
Problem This exception is unexpected. The cause is not immediately known.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWJP0020E: The Application Server cannot start the {0} module of the {1} application because the application is not installed.
Problem Verify that the {1} application is assembled correctly with the {0} module and installed.
User response Use an application assembly tool to verify the application configuration, install the application, and try again.
CWWJP0022I: The Java Persistence API (JPA) component is disabled.
Problem This message is for informational purposes only.
User response No action is required.
CWWJP0023E: The server cannot create an EntityManagerFactory instance for the {0} persistence unit for dependency injection into the {2} module of the {1} application.
Problem The {0} persistence unit and the dependency injection annotation must be defined properly.
User response Verify that the {0} persistence unit and the dependency injection annotation are defined properly. Try the process again.
CWWJP0024E: The {0} Java archive (JAR) file specification for the {2} persistence unit is incorrect.
Problem The JAR file specification for the {2} persistence unit is malformed. Therefore, the Java Persistence API (JPA) component is unable to supply this data to the persistence provider.
User response Correct the JAR file specification and try again.
CWWJP0025E: The server cannot identify the {0} Java Persistence API (JPA) root URL for the {2} module in the {1} application.
Problem The {0} JPA root URL for the {2} module in the {1} application is malformed.
User response If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWWJP0026I: The Java Persistence API (JPA) component is initializing.
Problem This message is for informational purposes only.
User response No action is required.
CWWJP0027I: The Java Persistence API (JPA) component has initialized.
Problem This message is for informational purposes only.
User response No action is required.
CWWJP0028I: The Java Persistence API (JPA) component is starting.
Problem This message is for informational purposes only.
User response No action is required.
CWWJP0029E: The server cannot find the {2} persistence unit in the {1} module and the {0} application.
Problem The {0} application has defined a persistence unit reference for the {2} persistence unit which cannot be found.
User response Make sure the {2} persistence unit is assembled correctly in the {0} application and try again.
CWWJP0030E: The server cannot locate the {0} data source in the component namespace for the {1} persistence unit. The following error occurred: {2}
Problem The data source defined for this persistence unit must be bound in the component namespace.
User response Ensure that the requested data source is created and bound in the java:comp/env namespace.
CWWJP0031E: The server cannot locate the {0} data source in the global namespace for the {1} persistence unit. The following error occurred: {2}
Problem The data source defined for this persistence unit must be bound in the global namespace.
User response Ensure that the requested data source is created and bound in the global namespace.
CWWJP0032E: The java.sql.Connection method invocation failed with error : {0}
Problem A java.sql.Connection method other than close method or isClosed method cannot be invoked because the server run time environment is not able to associate the operation thread with any Java Platform, Enterprise Edition 5 (Java EE 5) application component. This condition can occur when the Java Naming and Directory InterfaceTM (JNDI) client which is using the java: name, does not executed on the thread of a server application request.
User response Make sure that a Java EE 5 application does not run JNDI operations on java: names within static code blocks or in threads that are created by that J2EE application. This code does not necessarily run on the thread of a server application reques. Therefore, the code is not supported by JNDI operations on java: names.
CWWJP0033E: The server cannot locate the {0} data source in the component namespace for the {1} persistence unit because a component context does not exist on the thread.
Problem The {0} data source cannot be found because the server run time environment is not able to associate the operation thread with any Java Platform, Enterprise Edition 5 (Java EE 5) application component. This condition can occur when the Java Naming and Directory InterfaceTM (JNDI) client using the "java:" name does not run on the thread of a server application request.
User response Make sure that a Java EE 5 application does not run JNDI operations on java: names within static code blocks or in threads that are created by that J2EE application. This code does not necessarily run on the thread of a server application reques. Therefore, the code is not supported by JNDI operations on java: names.
CWWJP0034I: This message is an English-only Informational message: {0}.
Problem This informational message is not translated.
User response See message for details.
CWWJP0035W: This message is an English-only Warning message: {0}.
Problem This warning message is not translated.
User response See message for details.
CWWJP0036E: This message is an English-only Error message: {0}.
Problem This error message is not translated.
User response See message for details.
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.jpa.jpa.html

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