IBM Support

IC98984: WMQ ON WINDOWS: QUEUE MANAGER BECOMES UNRESPONSIVE AND MANY FDC FILES ARE GENERATED WITH PROBE ID XC308010 AND XC307100.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ queue managers running in a Windows domain
    environment become unresponsive as a result of a lack of
    response from the Domain controller.
    Applications connecting to WebSphere MQ queue managers are
    sometimes unable to connect and/or reconnect to the queue
    manager.
    
    Many FDCs will be generated with data similar to the following:
    Probe Id :- XC307100
    Component :- xlsRequestMutex
    Process Name :- ....\amqzlaa0.exe
    Major Errorcode :- xecL_W_LONG_LOCK_WAIT
    Probe Type :- MSGAMQ6150
    Probe Severity :- 3
    Probe Description :- AMQ6150: WebSphere MQ semaphore is busy.
    FDCSequenceNumber :- 11
    -----------------------
    MQM Function Stack
    zlaMainThread
    zlaProcessMessage
    zlaProcessMQIRequest
    zlaMQCONN
    zsqMQCONN
    kpiMQCONN
    kqiAuthorityChecks
    gpiCheckObjectAuthority
    zfu_as_checkobjectauthority
    zfu_as_calculateauthority
    zfuLockHashTable
    xlsRequestMutex
    xcsFFST
    +------------------+
    
    
    Probe Id :- XC308010
    Component :- xlsReleaseMutex
    Process Name :- ...\amqzlaa0.exe
    Major Errorcode :- xecL_W_LONG_LOCK_WAIT
    Probe Type :- MSGAMQ6150
    Probe Severity :- 3
    Probe Description :- AMQ6150: WebSphere MQ semaphore is busy.
    FDCSequenceNumber :- 5
    ----------------------
    MQM Function Stack
    zlaMainThread
    zlaProcessMessage
    zlaProcessSPIRequest
    zlaSPIKernel
    zsqSPIKernel
    kpiGeneric
    kqiCheckPrivileged
    gpiCheckPrivileged
    zfu_as_CheckPrivileged
    zfu_as_calculateauthority
    zfuUnlockHashTable
    xlsReleaseMutex
    xcsFFST
    
    
    If a WebSphere MQ trace is collected it can be identified that a
    WebSphere MQ agent process thread is hanging
    in the function xcsTimedLookupAccountName(). This in turn is
    blocking other threads requiring interprocess shared memory.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM WebSphere MQ with a domain controller, or
    active directory controller, which can be very slow to respond
    to requests.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    A queue manager wide lock was taken prior to making a query to
    the domain controller for user information, which was expected
    to complete very quickly. All new MQI operations are blocked
    whilst this query was completed, meaning that when the domain
    controller took a long time to respond, the queue manager
    appeared to hang and new work was not processed.
    

Problem conclusion

  • The locking in the code area which is responsible for querying
    the domain controller has been altered to ensure that the lock
    which was preventing other MQI calls from proceeding is not held
    whilst a request is made outside of MQ to the domain controller.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.6
    v7.5       7.5.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

    IC98984

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-27

  • Closed date

    2014-02-21

  • Last modified date

    2014-02-21

  • 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

  • R710 PSY

       UP

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

Document Information

Modified date:
09 March 2021