PH04012: CHANGING JPA SPEC LEVEL DOES NOT RESET PROVIDER IMPLEMENTATION CLASS IF ONE IS SET.

9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
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

• The "Default Java Persistence API settings" default Persistence
  Provider class setting, once set by the admin tooling, remains
  unchanged after changing the JPA Specification level. With
  respect to the bundled JPA Provider implementations, this will
  result with a server (or cluster members) having an incorrect
  value resulting with a NoClassDefFoundError when bootstrapping
  applications that use JPA.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Changing JPA Spec Level does not        *
  *                      remove stale JPA Provider Impl Class    *
  *                      name entry                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Changing the active JPA Spec Level between 2.0 and 2.1 does
  not remove any set value in the JPA Provider Implementation
  Class setting in the "Default JPA Persistence API Settings"
  controls.  This results in a NoClassDefFoundError when
  bootstrapping applications that use JPA.
  

Problem conclusion

• When the JPA Specification Level is changed in either wsadmin
  or the admin console, any default persistence provider class
  setting configured by the server or by any cluster member is
  removed.  The default class setting can be reconfigured
  after changing the JPA Specification Level.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.11.  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