IBM Support

PM26361: APPLICATIONS USING HIBERNATE MAY EXPERIENCE PERFORMANCE ISSUES DURING APPLICATION START

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The customer experienced a slow jvm start while using Hibernate
    and WebSphere Application Server 7.0.0.7.
    
    The following was found after reviewing javacores and finding
    that the JPA code was using a large percentage of the CPU on
    startup.
    
    " Applications using Hibernate that are ported from  WebSphere
    Application Server V6.1 to the Feature Pack for PM20625 or
    V7.0 may experience performance issues during application
    start.   This is due to a performance issue in Hibernate,
    however it is a regression since WebSphere invokes Hibernate
    code during application start that is not required when using
    Hibernate alone.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using Hibernate                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server Java       *
    *                      Persistence API (JPA) initialization    *
    *                      exposes a performance issue in          *
    *                      Hibernate.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server JPA initialization may invoke
    Hibernate methods during application start time.  This exposes
    a performance issue inside Hibernate (that will need to be
    addressed by them). This is especially noticeable when running
    in z/OS. If an application is using both Hibernate and
    WebSphere Application Server JPA this problem is unavoidable.
    However, if the application uses only Hibernate the JPA
    initialization is not needed.
    

Problem conclusion

  • The JVM System Property
    "com.ibm.websphere.persistence.ApplicationsExcludedFromJpaProces
    ssing" has been created to allow customers to disable
    WebSphere Application Server JPA initialization when it is not
    needed.
    
    Use the following instructions to enable this property.
    
    1. Open the administrative console.
    2. Select Servers -> Server Types -> WebSphere application
    servers.
    3. Select the server you want to configure.
    4. In the Server Infrastructure area, select Java and
    Process Management -> Process definition.
    5. In the Server Infrastructure area, select Process
    Definition.
    6. In the Additional Properties area, select Java Virtual
    Machine.
    7. In the Additional Properties area, select
    Custom Properties.
    8. Select the New box.
    9. In the Name entry field, type:
    com.ibm.websphere.persistence.ApplicationsExcludedFromJpaProcess
    ing
    10. In the Value entry field, type the names of the
    applications to be excluded from JPA processing.
    If there are multiple appliations separate each with the
    ":" character.  If you wish to specify all
    applications simply type the "*" character.
    11. Select OK.
    12. Restart the server.
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.15 and 6.1.0.35 (Feature Pack for EJB 3.0).
    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

    PM26361

  • Reported component name

    JPA OSGI FEATUR

  • Reported component ID

    5724J0857

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-09

  • Closed date

    2010-11-09

  • Last modified date

    2011-01-11

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

    PM20625

  • 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



Document information

More support for: WebSphere Application Server V7 Feature Pack for OSGi Applications and Java Persistence API 2.0
General

Software version: 1.0

Reference #: PM26361

Modified date: 11 January 2011