PM28820: EXCEPTION OCCURS WHEN OPENJPA PROCESS A PERSISTENCE UNIT WHERE THE PROVIDER IS NOT OPENJPA

PM28820; 7.0.0.13: exception occurs when openjpa process a persistence unit wher
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Product Release and Version Information: WebSphere Application
  Server V7.0 Base
  
  Problem Description:
  
  
  CWWJP0009E: The server cannot create an EntityManagerFactory
  factory for the TCT persistent unit from the
  org.hibernate.ejb.HibernatePersistence provider in
  jar:file:/WAS_Install_ROOT/profiles/AppSrv01/in
  stalledApps/CELLNAME/mycompany.ear/project.jar!/ module.
  

Local fix

• No Work Around Available
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V7.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: An application leveraging the Java      *
  *                      Persistence API (JPA) is configured to  *
  *                      utilize a JPA Persistence Provider      *
  *                      other then that which is shipped with   *
  *                      WebSphere Application Server 7.0.  A    *
  *                      problem with the application            *
  *                      environment (such as a <jar-file>       *
  *                      persistence unit element is declared,   *
  *                      but the jar file is missing in the      *
  *                      application classpath) is reported      *
  *                      by an Exception containing OpenJPA in   *
  *                      the stack trace instead of the          *
  *                      Persistence Provider intended by the    *
  *                      application.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The JPA implementation provided with WebSphere Application
  Server 7.0 may still attempt to validate <jar-file> entries in
  a persistence unit definition, even when an alternate JPA
  provider has been requested by the application.
  
  In situations where <jar-file> entries are missing from the
  application classpath, this could result in a confusing
  situation where OpenJPA is reporting the missing jar file
  entry instead of the requested alternate provider.
  

Problem conclusion

• This issue has been corrected with OpenJPA-1905.  OpenJPA will
  verify that it is the persistence provider intended for use by
  the application before attempting to validate that the
  <jar-file> elements are in the application classpath.  This
  ensures that this validation is properly handled and reported
  by the requested persistence provider instead of by OpenJPA.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.17.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM30908

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R700 PSY

     UP