PH07819: AFTER MIGRATING FROM WAS 8.5 TO 9.0 JPA 2.1 APPLICATION FAILS WITH CLASSNOTFOUNDEXCEPTION WHILE LOADING JPA CLASSES

9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3

APAR status

• Closed as program error.

Error description

• After migrating from WAS 8.5 to 9 application developed to use
  JPA 2.1 with the default persistence provider, dynamic import
  fails  from EclipseLink JPA bundle", with the
  ClassNotFoundException.
  java.lang.ClassNotFoundException:
  org.eclipse.persistence.jpa.PersistenceProvider
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  utilizing WAS' JPA 2.0 (EclipseLink)        *
  *                  implementation                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: ClassNotFoundException for WAS JPA      *
  *                      classes                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some cases, class loads initiated by application class
  loaders will fail to find WAS JPA (EclipseLink) classes, due to
  a failure by OSGi to resolve a dynamic import of the necessary
  package. There is no other error thrown from OSGi, and the
  class may be successfully loaded from within the OSGi
  framework.
  The issue is affected by bundle resolution ording and
  environmental factors, so it may not affect all users, and in
  some cases it has appeared after a fixpack or other
  environmental change (e.g. an OS update) was made to a system.
  

Problem conclusion

• An OSGi import/export duplication was removed, eliminating a
  conflict that led to the dynamic import failure.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.5.1.  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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP