IBM Support

IT17278: IBM MQ V8.0: FDCS REPORTING "AMQ6150: SEMAPHORE IS BUSY" ERRORS ARE TRUNCATED FOR THE FIRST INSTANCE FOR ALL PROCESSES.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • IBM MQ v8.0: Failure Data Capture (FDC) records are truncated
    when reporting "AMQ6150:
    WebSphere MQ semaphore is busy" and "Major Errorcode
    xecL_W_LONG_LOCK_WAIT."
    
    The initial instance is truncated prior to completion, and all
    other instances for the same PID do not generate additional FDC
    records.
    The disk has adequate space.
    
    The FDC records report the following:
    
    Probe Id :- XC307100
    Component :- xlsRequestMutex
    Program Name :- amqrmppa
    Major Errorcode :- xecL_W_LONG_LOCK_WAIT
    Probe Description :- AMQ6150: WebSphere MQ semaphore is busy
    FDCSequenceNumber :- 0
    
    and/or
    Probe Id :- XY551007
    Component :- xlsSpinLockRequest
    Program Name :- amqrmppa
    Major Errorcode :- xecL_W_LONG_LOCK_WAIT
    Probe Description :- AMQ6150: WebSphere MQ semaphore is busy
    FDCSequenceNumber :- 0
    
    The MQ log file AMQERR0x.LOG reports multiple instances
    for the same process id (PID). For each set of messages in the
    LOG file, there should be another instance of the FDC record for
    the
    same pid. Here is an example of the set of messages in the
    AMQERR0x.LOG:
    
    AMQ6150: WebSphere MQ semaphore is busy.
    
    AMQ6184: An internal WebSphere MQ error has occurred on queue
    manager TEST1.
    EXPLANATION:
    An error has been detected, and the WebSphere MQ error
    recording routine has been called. The failing process is
    process 11111.
    
    So each set of messages for process 11111 should have an
    instance of the FDC record. The FDCSequenceNumber will increase
    for
    each instance.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ V8 with clustered queue
    managers when MQ attempts to write an FDC record after an MQ
    process is blocked or hangs.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    An IBM MQ process encountered an error condition which caused it
    to write an FDC record.
    In order to dump certain internal structures, the FDC generation
    routine attempted to acquire a lock which was unavailable, and
    this caused the routine to hang.
    

Problem conclusion

  • The code has been fixed to ensure the FDC generation routine
    does not need to acquire the lock.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.7
    v9.0 CD    9.0.3
    v9.0 LTS   9.0.0.2
    
    
    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

    IT17278

  • 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-09-29

  • Closed date

    2017-02-27

  • Last modified date

    2017-02-27

  • 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:
27 February 2017