IBM Support

IV44522: Delayed write of error log message; and missing information in AMQ8024 message.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A message may be written out-of-order to the error log with
    respect to the times of other messages. The delay in writing
    that message may be up to 10 seconds.
    
    This may occur intermittently. For timing reasons, message
    AMQ8024 may be one such message that can be affected by this
    problem.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    You may be impacted by this problem if you are reading an MQ
    error log and expect messages to be in time order.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows)
    ****************************************************************
    PROBLEM SUMMARY:
    The out-of-order writing is caused by a queueing effect within
    the error logging process. There is a timing window where the
    processing of a queue can stall for up to 10 seconds, even when
    there are messages queued to be written to the error log.
    

Problem conclusion

  • The timing window in the queued processing of error messages has
    been eliminated.
    
    Please note however that in general there is no guarantee that
    message times in an error log will be strictly in time order.
    There may be rare occurrences of an out-of-order time stamp, for
    example due to slow CPU processing of a thread which has
    prepared a message, including its timestamp, but which has yet
    to actually issue the write of that message to the error log.
    That could allow a later-timestamped message to be written
    before that delayed message.
    
    The AMQ8024 message composition has been corrected to ensure
    that it includes the queue name.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
                       v7.1
    Platform           Fix Pack 7.1.0.4
    --------           --------------------
    Windows            7.1.0.4
    AIX                7.1.0.4
    HP-UX (Itanium)    7.1.0.4
    Solaris (SPARC)    7.1.0.4
    Solaris (x86-64)   7.1.0.4
    iSeries            7.1.0.4
    Linux (x86)        7.1.0.4
    Linux (x86-64)     7.1.0.4
    Linux (zSeries)    7.1.0.4
    Linux (Power)      7.1.0.4
    
    Version            v7.5
    --------           --------------------
    Fix available in:  7.5.0.3
    
    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

    IV44522

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-19

  • Closed date

    2013-07-03

  • Last modified date

    2013-07-03

  • 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 AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

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

Document Information

Modified date:
03 July 2013