IBM Support

IC79768: MESSAGES SET WITH A 25 DAY OR LONGER EXPIRY GO MISSING WHEN PUT FROM A WEBSPHERE MQ JAVA OR JMS CLIENT APPLICATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Messages set with a long expiry time, for example 30 days,
    and put to a WebSphere MQ queue using the WebSphere MQ V7
    classes for Java or JMS APIs, are found to go missing when the
    message is next browsed or received by an application.
    
    This includes attempting to browse the message using the
    WebSphere MQ Explorer, after it was put to the queue using the
    WebSphere MQ V7 classes for Java/JMS.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7 classes for Java.
    - The WebSphere MQ V7 classes for JMS.
    - The WebSphere MQ V7 Resource Adapter.
    - The WebSphere MQ V7 Explorer.
    - The WebSphere Application Server V6.1 WebSphere MQ messaging
    provider who have configured the WebSphere variable.
    - The WebSphere Application Server V7 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
    provider.
    MQ_INSTALL_ROOT to point to a WebSphere MQ V7 installation.
    
    This issue affects users of WebSphere MQ classes for Java/JMS
    who have received a message from a WebSphere MQ queue which had
    a defined expiry time to be greater than 24.8 days, and then
    put that message to a WebSphere MQ queue.
    
    This includes the scenario where a message which has exceeded
    its backout threshold value is received by a JMS application,
    resulting in the message being automatically moved to the
    backout destination by the WebSphere MQ classes for JMS.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    When the WebSphere MQ classes for Java/JMS received a WebSphere
    MQ message which had an MQMD expiry value which was equivalent
    to more than 24.8 days, or a literal MQMD numerical value of
    21,474,836 tenths of seconds, an internal algorithm incorrectly
    saved away the expiration value.
    
    The result of this was that if the message was put back to a
    WebSphere MQ queue, the message ended up containing the minimum
    expiration time of one tenth of a second defined in its MQMD.
    
    Any subsequent MQGET call on this message one tenth of a second
    later would result in the queue manager discarding the message.
    This includes browsing the message with the WebSphere MQ
    Explorer.  In this scenario, the queue would have a depth value
    which includes this message - but if the WebSphere MQ Explorer
    attempts to browse the message, the queue manager will assess
    the expiration time and discard the message.
    
    Note that if the queue manager is running on the z/OS platform,
    the queue manager has the ability to scan the queue
    periodically, searching for messages which have exceeded their
    expiration time.  In this case, the message could be expired
    before another application attempted to get or browse the
    message.
    

Problem conclusion

  • The WebSphere MQ classes for Java/JMS have been modified so that
    the algorithm correctly analyses the message's expiration value
    when the message is retrieved from the queue.
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.8
    --------           --------------------
    Windows            U200335
    AIX                U845856
    HP-UX (PA-RISC)    U847965
    HP-UX (Itanium)    U847970
    Solaris (SPARC)    U847966
    Solaris (x86-64)   U847972
    iSeries            7.0.1.8
    Linux (x86)        U847967
    Linux (x86-64)     U847971
    Linux (zSeries)    U847968
    Linux (Power)      U847969
    zOS                7.0.1.8
    
    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

    IC79768

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-11

  • Closed date

    2012-01-19

  • Last modified date

    2012-01-25

  • 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

  • R701 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.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 January 2012