IBM Support

PM20625: APPLICATIONS USING HIBERNATE MAY EXPERIENCE PERFORMANCE ISSUES DURING APPLICATION START ON WEBSPHERE V7

Fixes are available

6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

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

    PM20625

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-16

  • Closed date

    2010-09-16

  • Last modified date

    2010-09-16

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

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

    PM26361

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM20625

Modified date: 16 September 2010