IBM Support

IZ18142: ENDMQM CAN TAKE MANY MINUTES TO END THE QUEUE MANAGER IF THERE ARE ACTIVE SVRCONN CHANNELS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A customer using endmqm found that their queue manager
    would take up to 10 minutes to end if there were any SVRCONN
    channels running when the endmqm command was issued.
    
    No errors or FFSTs were reported. Hangdoc (SIGUSR2/amqldbgn)
    FFSTs revealed that endmqm is stuck inside rrxStopAllChannels fo
    a long time, even though the channel threads have all received
    MQRC_CONNECTION_BROKEN from their MQI calls.
    

Local fix

  • test fix supplied to customer
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who issue endmqm at a time when SVRCONN channels are
    active who need the queue manager to end quickly. There is a
    subtle timing condition which triggers the delay, so not all
    endmqm commands would be affected.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows)
    ****************************************************************
    PROBLEM SUMMARY:
    During endmqm processing, the endmqm command waits for all
    channel processes to end before it will exit.
    
    There was a defect in the error handling on WMQ SVRCONN
    channels such that the queue manager ending did not result
    in the channel thread shutting down. As a result, the channel
    thread kept running until it eventually timed out due to
    inactivity.
    
    Since endmqm waited for all channels to end, the channel
    delay caused endmqm to run for a long time.
    

Problem conclusion

  • The WMQ SVRCONN error handling has been corrected, so that
    queue manager shutdown is detected and SVRCONN channel
    threads will now shut down promptly in response to the
    queue manager ending.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v6.0
    Platform           Fix Pack 6.0.2.5
    --------           --------------------
    Windows            U200292
    AIX                U815929
    HP-UX (PA-RISC)    U815636
    HP-UX (Itanium)    U815818
    Solaris (SPARC)    U815659
    Solaris (x86-64)   U815928
    iSeries            tbc
    Linux (x86)        U815767
    Linux (x86-64)     U815808
    Linux (zSeries)    U815805
    Linux (Power)      U815806
    Linux (s390x)      U815807
    
    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

    IZ18142

  • Reported component name

    WMQ LIN X86 V6

  • Reported component ID

    5724H7204

  • Reported release

    601

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-03-20

  • Closed date

    2008-03-28

  • Last modified date

    2008-03-28

  • 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 LIN X86 V6

  • Fixed component ID

    5724H7204

Applicable component levels

  • R600 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ5M","label":"APAR"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 March 2008