IBM Support

IT09769: MQRC_OFFSET_ERROR from amqrrmfa or amqzlaa0 processes. Queue manager can end immediately.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • FDCs are written by the MQ Cluster Repository Manager
    (amqrrmfa).  The problem is more likely following a REFRESH
    CLUSTER command, but can be seen without it.  amqrrmfa or
    amqzlaa0 threads can end after reporting SIGSEGV memory
    exceptions.  The queue manager can end immediately, or after a
    period of time while AMQ9448 and AMQ9449 error messages are
    written to the error logs.
    
    Examples of the FDC probes that can be seen:
    
    Probe Id :- RM194019
    Component :- rrmMakePCF
    Program Name :- amqrrmfa
    MQM Function Stack ends with:
    rrmMaintenance
    rfxEnumCLQ
    rrmMaintainClq
    rrmUpdateClq
    rrmPubForClq
    rrmMakePCF
    xcsFFST
    Missing PCF segment: Zero Length provided.
    
    Probe Id :- RM413001
    Component :- rfxLINK
    Major Errorcode :- MQRC_OFFSET_ERROR
    MQM Function Stack ends with:
    rfxAddCLQ
    rfiAllocCacheArea
    rfxLINK
    xcsFFST
    
    Probe Id :- RM220005
    Component :- rrmRepository
    Program Name :- amqrrmfa
    
    Probe Id :- RM247030
    Component :- rfiFreeCacheArea
    Program Name :- amqrrmfa
    MQM Function Stack ends with:
    rfxCheckRegister
    rfiCheckQueueRegister
    rfiFreeCacheArea
    xcsFFST
    
    Probe Id :- XC130004
    Component :- xehExceptionHandler
    Program Name :- amqrrmfa
    Arith1 :- 11 (0xb)
    Comment1 :- SIGSEGV
    MQM Function Stack ends with:
    rfxAddCLQ
    rfiAllocCacheArea
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere MQ V7 and later in a clustered environment.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A timing window existed such that if a cluster queue object was
    refreshed while it is simultaneously held open by an
    application, there was a risk that the internal cluster cache
    for cluster definitions could become invalid.
    

Problem conclusion

  • The WebSphere MQ clustering code has been modified to correctly
    update
    the internal cluster cache when refreshing cluster queue
    objects.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.14
    v7.1       7.1.0.8
    v7.5       7.5.0.6
    v8.0       8.0.0.4
    
    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

    IT09769

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-30

  • Closed date

    2015-10-23

  • Last modified date

    2017-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 BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 June 2020