Explanation | 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} |
Action | 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. |
Explanation | 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} |
Action | Inspect the {0} JPA provider bundle to make sure that the META-INF/services/javax.persistence.spi.PersistenceProvider file exists and is correctly formatted. |
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 {0} 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 your 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 {2} 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 enterprise archive (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 executed on the thread of a server application request. |
Action | 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. |
Explanation | 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. |
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 {0} application is either not installed or has not been started. |
Action | Install or start the {0} 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 {0} data source for the {1} persistence unit. However, a data source cannot be found. |
Action | Make sure that the requested data source is created and bound. |
Explanation | 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. |
Action | Correct the corrupt class file or contact the JPA provider for assistance. |
Explanation | The {0} Java Persistence API (JPA) provider createContainerEntityManagerFactory method failed with the following error: {2} |
Action | Contact the JPA provider for assistance. |
Explanation | More than one {0} persistence context reference is declared in the {1} 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 | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The {0} 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 | This exception is unexpected. The cause is not immediately known. |
Action | 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/. |
Explanation | Verify that the {1} application is assembled correctly with the {0} module and installed. |
Action | Use an application assembly tool to verify the application configuration, install the application, and try again. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The {0} persistence unit and the dependency injection annotation must be defined properly. |
Action | Verify that the {0} persistence unit and the dependency injection annotation are defined properly. Try the process again. |
Explanation | 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. |
Action | Correct the JAR file specification and try again. |
Explanation | The {0} JPA root URL for the {2} module in the {1} application is malformed. |
Action | 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/. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The {0} application has defined a persistence unit reference for the {2} persistence unit which cannot be found. |
Action | Make sure the {2} persistence unit is assembled correctly in the {0} application and try again. |
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 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. |
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 executed 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 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. |
Explanation | 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. |
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 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. |
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. |