IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

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 number

    PH04012

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-15

  • Closed date

    2018-12-10

  • Last modified date

    2018-12-10

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 900

Reference #: PH04012

Modified date: 10 December 2018