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

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 IBM WebSphere Application Server Feature*
  *                  Pack for OSGi Applications and JPA 2.0 users
  ****************************************************************
  * PROBLEM DESCRIPTION: Application startup fails because       *
  *                      OpenJPA validation is reporting a       *
  *                      missing                                 *
  *                      <jar-file> entry in the application     *
  *                      classpath, when the application had     *
  *                      overridden the default JPA              *
  *                      Persistence Provider to a non-OPENJPA   *
  *                      provider.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The JPA implementation provided with WebSphere Application
  Server Feature Pack for OSGi Applications and JPA 2.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 1.0.0.5. 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:

  PM28820

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

Fix information

• Fixed component name

  JPA OSGI FEATUR

• Fixed component ID

  5724J0857

Applicable component levels

• R700 PSY

     UP