IBM Support

PH01742: FIX PACK 9.0.0.7 OR 9.0.0.8, DIDN'T UPDATE JPA CONFIGURATION FILE CORRECTLY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Fix pack 9.0.0.7 or 9.0.0.8, didn't update JPA configuration
    file correctly, so caused error reported:
    ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper
    service SRVE0014E: Uncaught service() exception root cause
    Faces Servlet: javax.servlet.ServletException:
    javax.el.ELException: <openjpa-2.2.3-SNAPSHOT-r422266:1827923
    nonfatal general error>
    org.apache.openjpa.persistence.PersistenceException:
    Instantiation of plugin "DataCacheManager" with value
    "dynacache" caused an error
    "java.lang.IllegalArgumentException:
    java.lang.ClassNotFoundException: dynacache". The alias or
    class name may have been misspelled, or the class may not have
    be available in the class path. Valid aliases for this plugin
    are: [default]
    at
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:230)
    ...
    Caused by: java.lang.IllegalArgumentException:
    java.lang.ClassNotFoundException: dynacache
    at serp.util.Strings.toClass(Strings.java:164)
    at serp.util.Strings.toClass(Strings.java:108)
    at
    org.apache.openjpa.lib.conf.Configurations.newInstance(Configu
    ra tions.java:216)
    

Local fix

  • manually copy
    $WAS_HOME/properties/selectableBundles/jpa-2.0.xml to each
    <profile_home>/servers/<server_name>/configuration/wsBundleMetad
    ata,
    OR
    changing the active JPA specification level to 2.1, save the
    configuration between the spec level change,  The xml file will
    only be changed when saved (and propagated to the nodes if on
    ND).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  Java(tm) Persistence API 2.0 (jpa-2.0)      *
    ****************************************************************
    * PROBLEM DESCRIPTION: After updating WebSphere Application    *
    *                      Server, an application fails with a     *
    *                      PersistenceException caused by a        *
    *                      ClassNotFoundException on class         *
    *                      "dynacache"                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After updating an installation to version 9.0.0.7
    or greater, an application that uses jpa-2.0 may throw the
    following exception:
    org.apache.openjpa.persistence.PersistenceException:
    Instantiation of plugin "DataCacheManager" with
    value "dynacache" caused an error
    "java.lang.IllegalArgumentException:
    java.lang.ClassNotFoundException: dynacache". The alias or
    class name may have been misspelled, or the class may not have
    be available in the class path. Valid aliases for this plugin
    are: [default]
    at
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:230)
    ...
    Caused by: java.lang.IllegalArgumentException:
    java.lang.ClassNotFoundException: dynacache
    at serp.util.Strings.toClass(Strings.java:164)
    at serp.util.Strings.toClass(Strings.java:108)
    at
    org.apache.openjpa.lib.conf.Configurations.newInstance(Configura
    tions.java:216)
    ...
    The exception occurs because the descriptor which defines
    the OSGi bundle provision for jpa-2.0 changed in 9.0.0.7, but
    the change did not apply to the application server's
    configuration during the update. The obsolete descriptor causes
    the application server to start without provisioning the
    DataCacheManager(dynacache) plugin, which in turn causes the
    ClassNotFoundException shown above.
    

Problem conclusion

  • Apply APAR PH01742 to ensure the application server provisions
    the appropriate OSGi bundles whenever jpa-2.0 is enabled.
    
    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

  • There are two ways to resolve this problem on a server without
    applying APAR PH01742.
    
    1. Manually copy file
    
    <was_home>/properties/selectableBundles/jpa-2.0.xml
    
    To directory
    
    <profile_home>/servers/<server_name>/configuration/wsBundleMetad
    ata
    
    Or,
    
    2. Change the server's JPA specification level to
    jpa-2.1, save the change; and when using WAS Network
    Deployment, synchronize the change to the node. Then, change
    the server's JPA specification level back to jpa-2.0, save and
    synchronize the change.
    
    Run the osgiCfgInit utility on the server to reset the
    server's OSGi bundle cache.
    
    <profile_home>/bin> ./osgiCfgInit.sh -servers <server_name>
    
    The change will be effective upon restarting the server.
    

Comments

APAR Information

  • APAR number

    PH01742

  • 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-08-15

  • Closed date

    2018-11-12

  • Last modified date

    2018-12-06

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021