IBM Support

IC74233: MESSAGE NOT ROLLED BACK AFTER WMQ V7 JMS CLIENT APPLICATION CRASHES AFTER AN OUTOFMEMORYERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A WebSphere MQ v7 JMS client connects to a WMQ v7 queue manager
    and receives a message using asynchronous delivery.  The message
    is larger than the heap and it causes the application to fail
    with an out of memory error (OOM),
    java.lang.OutOfMemoryErrorjava.lang.OutOfMemoryError.
    
    After the OOM, the JMS application receives a smaller message
    which does not cause an OOM and this message is successful
    and is acknowledged by the application.
    
    The previous message which caused the OOM error, which was
    implicitly acknowledged even though it was not actually received
    by the application, is lost.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This problem affects users of WMQ V7 classes for JMS receiving
    messages asynchronously and having insufficient memory to run
    the WMQ JMS client application.
    
    The APAR affects users of WebSphere Application Server who use
    message driven beans to receive messages.
    
    The APAR also affects users of the WebSphere MQ (WMQ)
    Resource Adapter who use MDB's to receive messages.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    When the WebSphere MQ V7 classes for JMS received an
    OutOfMemoryError when asynchronously receiving a message,the
    classes for JMS would not handle the error and simply try to
    receive another message.
    
    If there was sufficient memory to receive the next message,
    then the WebSphere MQ V7 classes for JMS would deliver this
    message to the application that was monitoring the queue where
    the message was. The message that was being processed when the
    OutOfMemoryError occurred, was lost.
    

Problem conclusion

  • The WebSphere MQ V7 classes for JMS have been updated to catch
    an OutOfMemoryError when asynchronously receiving messages.
    When this exception occurs, the thread responsible for
    receiving messages asynchronously is stopped immediately. The
    message that was being processed when the error occurred is
    left on the queue, so that it can be reprocessed at a later
    date.
    
    The JMS connection is also notified of the error. The
    connection will then take appropriate action, which may or may
    not succeed depending on how much memory is available to the
    Java runtime environment.
    
    Following the OutOfMemoryError, the application that was
    asynchronously receiving messages needs to be restarted in
    order to process messages again.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.6
    --------           --------------------
    Windows            U200328
    AIX                U840698
    HP-UX (PA-RISC)    U841555
    HP-UX (Itanium)    U841560
    Solaris (SPARC)    U841556
    Solaris (x86-64)   U841562
    iSeries            tbc_p700_0_1_6
    Linux (x86)        U841557
    Linux (x86-64)     U841561
    Linux (zSeries)    U841558
    Linux (Power)      U841559
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC74233

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-01

  • Closed date

    2011-04-04

  • Last modified date

    2011-04-04

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 April 2011