IBM Support

IT15087: FDC WITH PROBEID AO173001 GENERATED WHEN PROCESSING MQSUB REQUEST

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A Failure Data Capture (FDC) file may be generated generated
    similar to the one below when an MQ channel agent receives an
    MQSUB API call.
    The issue has been observed with a queue manager running on the
    MQ Appliance, but could also affect queue managers on
    distributed operating systems.
    
    
    +---------------------------------------------------------------
    --------------+
    |
                  |
    | WebSphere MQ First Failure Symptom Report
                                      |
    | =========================================
                                      |
    |
                  |
    | Component         :- aouLockObjectCatalogue
                                    |
    | SCCS Info         :-
    /build/slot1/p800_P/src/lib/lqm/amqaoula.c,            |
    | Line Number       :- 147
                                                       |
    | Program Name      :- amqrmppa
                                                  |
    | Arguments         :- -m QMA
                                                    |
    | Addressing mode   :- 64-bit
                                                    |
    | LANG              :-
                                                           |
    | Process           :- 140221
                                                    |
    | Process(Thread)   :- 140422
                                                    |
    | Thread            :- 171    RemoteResponder
                                    |
    | QueueManager      :- QMA
                                                       |
    | UserApp           :- FALSE
                                                     |
    | ConnId(1) IPCC    :- 399
                                                       |
    | ConnId(2) QM      :- 19255
                                                     |
    | ConnId(3) QM-P    :- 343
                                                       |
    | Last HQC          :- 2.5.5-23020160
                                            |
    | Last HSHMEMB      :- 2.13.24-837184
                                            |
    | Last ObjectName   :-
                                                           |
    | Major Errorcode   :- krcE_UNEXPECTED_ERROR
                                     |
    | Minor Errorcode   :- OK
                                                        |
    | Probe Type        :- INCORROUT
                                                 |
    | Probe Severity    :- 2
                                                         |
    | Probe Description :- AMQ6125: An internal IBM MQ Appliance
    error has        |
    |   occurred.
    
    | FDCSequenceNumber :- 0
                                                         |
    |
                  |
    +---------------------------------------------------------------
    --------------+
    
    MQM Function Stack
    ccxResponder
    rrxResponder
    ccxReceiveThreadFn
    cciProcessOne
    cciProcessUserData
    cciProcessAsyncRcv
    rriServerAsyncRcv
    rriMQIServerReceive
    rriMQIServerCall
    rriProcessSubscribe
    zstMQSUB
    zifMQSUB
    zsqMQSUB
    kpiMQSUB
    kqiSubscribeTopic
    kqiCreateSubscription
    kqiSetupDestQForNewSub
    kqiOpenIt
    kqiOpenQueue
    kqiOpenModel
    apiRaiseMinorQueue
    aocCreateMinorQueue
    aouLockSynChain
    xcsFFST
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who make multiple concurrent attempts to create new MQ
    objects of the same name.
    
    This is most likely to be the creation of a fixed name dynamic
    queue, where the dynamic queue is created upon first reference,
    for example the detection that a fixed name temporary dynamic
    queue has already been created through the returning of an
    MQRC_OBJECT_ALREADY_EXISTS on the corresponding MQOPEN.
    
    
    Platforms affected:
    AIX, HP-UX Itanium, HP-UX PA-RISC, IBM iSeries, Linux on S390,
    Linux on x86, Linux on x86-64, Linux on zSeries, Solaris SPARC,
    Solaris x86-64, Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Creating a new MQ object involves a number of complex lock
    interactions.
    MQ's locks are arranged in a strict hierarchy, to avoid the
    possibility of deadlock, and the code that detects that the same
    named object has unexpectedly been created in a window between
    checking for the objects existence, and creating the object
    contained a programming error which resulted in a lock not being
    released when it should have been.
    

Problem conclusion

  • The MQ queue manager code has been corrected to avoid the
    possibility of this lock unexpectedly not being released.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.5
    
    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

    IT15087

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-04

  • Closed date

    2016-08-01

  • Last modified date

    2017-03-10

  • 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

  • R800 PSY

       UP

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

Document Information

Modified date:
10 March 2017