IBM Support

PM19940: OutOfMemoryError error occurs while invoking a JAX-RPC Web service.

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

  • A client application containing a large number of JAX-RPC web
    Service invocations on multiple threads may fail with a
    OutOfMemoryError error.
    
    The heapdump (or php file) associated with the failure
    indicated that the
    com.ibm.ws.webservices.engine.encoding.ser.EnumDerserializer
    object is holding a reference to a
    com.ibm.ws.webservices.engine.encoding.DeserializationContextImp
    l object.  The DeserializationContextImpl object and its
    objects consume a large amount of memory, which causes the
    OutOfMemoryError exception.
    
    A customer may notice this large memory usage while using the
    HeapAnalyzer tool or another heap analysis tool.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-RPC                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: An OutOfMemoryError error may occur     *
    *                      when a large number of JAX-RPC          *
    *                      Web services are invoked across         *
    *                      multiple threads.                       *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR.     *
    ****************************************************************
    A client application containing a large number of JAX-RPC web
    Service invocations on multiple threads may fail with a
    OutOfMemoryError error.
    
    The heapdump (or php file) associated with the failure
    indicated that the
    com.ibm.ws.webservices.engine.encoding.ser.EnumDeserializer
    object is holding a reference to a
    com.ibm.ws.webservices.engine.encoding.DeserializationContextImp
    l object.  The DeserializationContextImpl object and its
    objects consume a large amount of memory, which causes the
    OutOfMemoryError exception.
    
    You may notice this large memory usage while using the
    HeapAnalyzer tool or another heap analysis tool.
    
    Note: In the failing scenario, over 100 threads were being
    used by the application.  In addition, the JAX-RPC Web
    services were large and complicated.  This combination of
    heavy load exposed OutOfMemoryError error.  Most customers
    will not be susceptible to this error.
    

Problem conclusion

  • In the failing scenario, the client application is calling a
    large number of JAX-RPC applications on many (>100) threads.
    
    This type of usage increases the memory footprint of the
    JAX-RPC engine.   The high workload exposed a flaw in the
    JAX-RPC engine related to the JAX-RPC enumeration deserializer.
    The extra memory consumed by the enumeration deserializer
    caused the OutOfMemoryError error.
    
    The EnumDeserializer is changed to remove the reference to the
    DeserializationContext.  This change does not affect the logic
    of the code, but significantly reduces the amount of memory
    that is held.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.3.35 and 7.0.0.15.  The 6.0.2 solution is not
    in a fixpack.
    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

    PM19940

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-05

  • Closed date

    2010-08-17

  • Last modified date

    2010-08-17

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • 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: 6.0

Reference #: PM19940

Modified date: 17 August 2010