IBM Support

IT19227: dmpmqcfg times out waiting for responses from the command serverwhen the queue manager has many objects defined

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The queue manager has many objects, or is running on a slow
    machine.
    
    The dmpmqcfg command runs for approximately 30-60 seconds, then
    ends with a timeout error:
    
    "MQSC timed out waiting for a response from the command server."
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of dmpmqcfg attempting to dump definitions from a queue
    manager that is running slowly due to resource restrictions,
    and/or has many objects defined.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    dmpmqcfg works by sending "inquire" commands the command server,
    and receiving responses.  If the queue manager (or its command
    server, or the machine it is running on) is busy, then the
    responses can take a "long" time to come back.
    
    When it has sent the requests, the main routine of dmpmqcfg
    enters a loop waiting for all work to be complete on a separate
    thread.
    
    In this loop, every 30 seconds, a health check is done.  The
    health check looks at the number of commands processed, and if
    this number has not increased since the last time we checked
    (ie. 30 seconds ago) then dmpmqcfg assumes a failure has
    happened, and ends the program.
    
    But this condition also happens in the case documented here: the
    queue manager is slow in responding for reasons of resource
    shortage or large number of definitions.
    

Problem conclusion

  • A command line switch -w has been added to dmpmqcfg.  Via this
    switch the user can supply an argument which is the acceptable
    timeout when waiting for a reply message from the command
    server.  The default is 60 seconds.
    
    So, for example, to use a value of 120 seconds:
    
    dmpmqcfg -m QMNAME -a -w 120
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.9
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    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

    IT19227

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-12

  • Closed date

    2017-05-30

  • Last modified date

    2017-05-30

  • 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

    5724H7241

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 May 2017