CWWJP

Express (Distributed operating systems), v8.0 > Reference > Messages

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}

Explanation During server processing for the default JPA provider, the server was not able to find the file for the provider in the bundle.
Action Inspect the 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 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}

Explanation During server processing for the default JPA provider, the server cannot read the content of a file in the JPA provider bundle.
Action Inspect the 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.

Explanation 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 extended persistence context within the scope of a different bean type.
Action 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.

Explanation 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.
Action Contact the 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.

Explanation To enable full JPA support, a persistence provider might need to inject code into a JPA entity. The active ClassLoader type does not support JPA code injection. Therefore, a JPA entity might not work as expected.
Action No action is required.

CWWJP0006I: The {0} class is loaded as the default Java Persistence API (JPA) provider.

Explanation This message is for informational purposes only.
Action No action is required.

CWWJP0007W: The {0} persistence unit in the {2} module of the {1} application is already defined.

Explanation 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 EAR file. The duplicate persistence unit will be ignored.
Action 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}

Explanation 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 run on the thread of a server application request.
Action Make sure that a Java EE 5 application does not run 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 EntityManagerFactory factory for the {0} persistent unit from the {1} provider in {2} module.

Explanation The Java Persistence API (JPA) provider createContainerEntityManagerFactory method failed to return an EntityManagerFactory. This might occur if the incorrect JPA provider is used for the persistent unit, or an error occurred in the JPA provider.
Action 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.

Explanation The application is either not installed or has not been started.
Action Install or start the application.

CWWJP0012E: The persistence unit name is not specified and a unique persistence unit is not found in the {0} application and {1} module.

Explanation The application has defined a persistence unit or persistence context reference without a persistence unit name and a unique persistence unit cannot be found.
Action 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}.

Explanation The server has attempted to locate the data source for the persistence unit. However, the data source could not be found.
Action 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.

Explanation The Java Persistence API (JPA) provider has attempted to transform a class and failed with an IllegalClassFormatException. Either the class file is corrupted or the JPA provider has a problem.
Action Correct the corrupted 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}

Explanation The Java Persistence API (JPA) provider createContainerEntityManagerFactory method failed.
Action 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.

Explanation More than one persistence context reference is declared in the deployment description file. All instances, except for the first instance, are ignored.
Action Before trying again, rename or remove the duplicate persistence context reference.

CWWJP0017I: The Java Persistence API (JPA) component has started.

Explanation This message is for informational purposes only.
Action No action is required.

CWWJP0018E: Incorrect syntax or error detected in the {0} file. The following associated error message occurred: {1}

Explanation A XML file contains an error or errors and does not conform to the schema definition. The application might not function as expected.
Action Correct the error or errors in the persistence.xml file and try again.

CWWJP0019W: The {0} application has already started.

Explanation This exception is unexpected. The cause is not immediately known.
Action More info at:

WAS Support page
WAS for z/OS Support page

CWWJP0020E: The Application Server cannot start the {0} module of the {1} application because the application is not installed.

Explanation Verify that the application is assembled correctly with the module and installed.
Action 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.

Explanation This message is for informational purposes only.
Action 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.

Explanation The persistence unit and the dependency injection annotation must be defined properly.
Action Verify that the persistence unit and the dependency injection annotation are defined properly. Try the process again.

CWWJP0024E: The {0} JAR file specification for the {1} persistence unit is incorrect.

Explanation The JAR file specification for the persistence unit is malformed. Therefore, the Java Persistence API (JPA) component is unable to supply this data to the persistence provider.
Action 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.

Explanation The JPA root URL for a module in the application is malformed.
Action More info at:

WAS Support page
WAS for z/OS Support page

CWWJP0026I: The Java Persistence API (JPA) component is initializing.

Explanation This message is for informational purposes only.
Action No action is required.

CWWJP0027I: The Java Persistence API (JPA) component has initialized.

Explanation This message is for informational purposes only.
Action No action is required.

CWWJP0028I: The Java Persistence API (JPA) component is starting.

Explanation This message is for informational purposes only.
Action No action is required.

CWWJP0029E: The server cannot find the {2} persistence unit in the {1} module and the {0} application.

Explanation An application has defined a persistence unit reference for a persistence unit that could not be found after searching for META-INF/persistence.xml in all files and directories on the classpath.
Action Ensure that the persistence unit name is spelled properly, and ensure that the persistence unit is assembled correctly in the application by verifiying that the persistence unit is defined in a META-INF/persistence.xml file that is in a JAR or directory on the classpath.

CWWJP0030E: The server cannot locate the {0} data source in the component namespace for the {1} persistence unit. The following error occurred: {2}

Explanation The data source defined for this persistence unit must be bound in the component namespace.
Action 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}

Explanation The data source defined for this persistence unit must be bound in the global namespace.
Action 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}

Explanation 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 run on the thread of a server application request.
Action 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 Java EE 5 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.

Explanation The 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.
Action 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 Java EE 5 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}.

Explanation This informational message is not translated.
Action See message for details.

CWWJP0035W: This message is an English-only Warning message: {0}.

Explanation This warning message is not translated.
Action See message for details.

CWWJP0036E: This message is an English-only Error message: {0}.

Explanation This error message is not translated.
Action See message for details.

CWWJP0037E: The Unit Of Work Synchronization Registry could not be found at the {0} location in the global namespace due to exception: {1}

Explanation A Java Persistence API (JPA) provider cannot function properly without access to the UOWSynchronizationRegistry to participate in transactions.
Action More info at:

WAS Support page
WAS for z/OS Support page

CWWJP0038E: The requested Java Persistence API (JPA) method for the {0} persistence context could not be completed because it was called outside the scope of a Java Platform, Enterprise Edition 5 (Java EE 5) application component.

Explanation The component context does not exist on the thread. 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 client attempts EntityManager operations on a non-server application thread.
Action Make sure that a Java EE 5 application does not run EntityManager operations within static code blocks or in threads that are created by the Java EE application.

CWWJP0039E: A syntax error exists within the properties within the persistence.xml of Persistence Unit: {0} (Property = {1}, Value = {2}). The following error occurred: {3}.

Explanation The persistence.xml for the persistence unit contains a syntax error. Neither the property nor the value may have a value of "null".
Action Fix the syntax error that exists in the persistence.xml.

CWWJP0040E: Incorrect syntax or error detected in the persistence.xml file in application: {0}, module: {1}, at line number: {2}, column number: {3}. The following associated error message occurred: {4}

Explanation A persistence.xml file contains an error or errors and does not conform to the schema definition. The application might not function as expected.
Action Correct the error or errors in the persistence.xml file and try again.

CWWJP0041E: The {0} module of the {1} application has conflicting configuration data in the XML deployment descriptor. Conflicting {2} element values exist for multiple {3} elements with the same {4} element value : {5}. The conflicting {2} element values are {6} and {7}.

Explanation When multiple persistence unit or persistence context references are defined in the XML deployment descriptor for the same component namespace with the same name, all attributes of the reference must be the same. A typical scenario where this may occur is when defining references for an enterprise bean and for a corresponding interceptor class. Both the bean and the interceptor share the same component namespace, so references that are common between the two must be compatible.
Action In the XML deployment descriptor, change the name of one of the references, or change one of the conflicting values so they are the same value.

CWWJP9990I: {0}

Explanation The Java Persistence API (JPA) provider has logged this informational message.
Action See the JPA provider documentation.

CWWJP9991W: {0}

Explanation The Java Persistence API (JPA) provider has logged this warning message.
Action See the JPA provider documentation.

CWWJP9992E: {0}

Explanation The Java Persistence API (JPA) provider has logged this error message.
Action See the JPA provider documentation.

CWWJP9993E: {0}

Explanation The Java Persistence API (JPA) provider has logged this fatal message.
Action See the JPA provider documentation.

+
Search Tips | Advanced Search

Explanation	During server processing for the default JPA provider, the server was not able to find the file for the provider in the bundle.
Action	Inspect the 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 JAR file is specified in the Bundle-ClassPath property in the META-INF/MANIFEST.MF file.

Explanation	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 extended persistence context within the scope of a different bean type.
Action	Modify the application to initiate the extended persistence context within the scope of a stateful session bean, or change the persistence context.

Explanation	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.
Action	Contact the system administrator to make a user-defined or the default system WSJPA implementation accessible to the application server.

Explanation	To enable full JPA support, a persistence provider might need to inject code into a JPA entity. The active ClassLoader type does not support JPA code injection. Therefore, a JPA entity might not work as expected.
Action	No action is required.

Explanation	This message is for informational purposes only.
Action	No action is required.

Explanation	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 EAR file. The duplicate persistence unit will be ignored.
Action	Before trying again, rename or remove the duplicate persistence unit.

Explanation	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 run on the thread of a server application request.
Action	Make sure that a Java EE 5 application does not run 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.

Explanation	The Java Persistence API (JPA) provider createContainerEntityManagerFactory method failed to return an EntityManagerFactory. This might occur if the incorrect JPA provider is used for the persistent unit, or an error occurred in the JPA provider.
Action	Make sure the correct JPA provider has been configured for the persistent unit, and check for any previous errors from the JPA privider.

Explanation	The application is either not installed or has not been started.
Action	Install or start the application.

Explanation	The application has defined a persistence unit or persistence context reference without a persistence unit name and a unique persistence unit cannot be found.
Action	Change the application to specify a persistence unit name for the reference, or provide a unique persistence.

Explanation	The server has attempted to locate the data source for the persistence unit. However, the data source could not be found.
Action	Make sure that the requested data source is created and bound.

Explanation	More than one persistence context reference is declared in the deployment description file. All instances, except for the first instance, are ignored.
Action	Before trying again, rename or remove the duplicate persistence context reference.

Explanation	A XML file contains an error or errors and does not conform to the schema definition. The application might not function as expected.
Action	Correct the error or errors in the persistence.xml file and try again.

Explanation	Verify that the application is assembled correctly with the module and installed.
Action	Use an application assembly tool to verify the application configuration, install the application, and try again.

Explanation	The persistence unit and the dependency injection annotation must be defined properly.
Action	Verify that the persistence unit and the dependency injection annotation are defined properly. Try the process again.

Explanation	The JAR file specification for the persistence unit is malformed. Therefore, the Java Persistence API (JPA) component is unable to supply this data to the persistence provider.
Action	Correct the JAR file specification and try again.

Explanation	An application has defined a persistence unit reference for a persistence unit that could not be found after searching for META-INF/persistence.xml in all files and directories on the classpath.
Action	Ensure that the persistence unit name is spelled properly, and ensure that the persistence unit is assembled correctly in the application by verifiying that the persistence unit is defined in a META-INF/persistence.xml file that is in a JAR or directory on the classpath.

Explanation	The data source defined for this persistence unit must be bound in the component namespace.
Action	Ensure that the requested data source is created and bound in the java:comp/env namespace.

Explanation	The 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.
Action	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 Java EE 5 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.

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	The component context does not exist on the thread. 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 client attempts EntityManager operations on a non-server application thread.
Action	Make sure that a Java EE 5 application does not run EntityManager operations within static code blocks or in threads that are created by the Java EE application.

Explanation	The persistence.xml for the persistence unit contains a syntax error. Neither the property nor the value may have a value of "null".
Action	Fix the syntax error that exists in the persistence.xml.

Explanation	A persistence.xml file contains an error or errors and does not conform to the schema definition. The application might not function as expected.
Action	Correct the error or errors in the persistence.xml file and try again.