IBM Support

IV37602: WEBSHPERE MQ .NET CLIENT APPLICATION MESSAGE DELIVERY HANGS AND QUEUE STATUS BECOMES "SUSPENDED"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Out of many call backs registered by the .Net client
    application, few of them have their call back suspended and
    message delivery hangs. No errors explaining the reason in MQ
    server logs and no exceptions are thrown to the application.
    
    The runmqsc command "Display conn" has the following output.
    Note the attribute: ASTATE(SUSPENDED)
    ..
    QUEUE(SYSTEM.MANAGED.NDURABLE.4FEx)
    TYPE(HANDLE)                            APPLDESC(WebSphere
    MQ Channel)
    APPLTAG(xxx)   APPLTYPE(SYSTEM)
    BROWSE(NO)                              CHANNEL(yyy)
    CONNAME(1.2.3.4)                   ASTATE(SUSPENDED)
    HSTATE(INACTIVE)                        INPUT(SHARED)
    INQUIRE(YES)                            OUTPUT(NO)
    PID(xxx)                            QMURID(0.0)
    SET(NO)                                 TID(*)
    URID(XA_FORMATID[00000000] XA_GTRID[] XA_BQUAL[])
    URTYPE(QMGR)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of .NET applications with Read Ahead enabled which run as
    asynchronous consumers
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    QueueStatus - "ASTATE" attribute gets into SUSPENDED state to
    indicate that the server side has put it into this state, not
    directly the client code. Server decides not to send any further
    messages up to the client since Read ahead is enabled and the
    client couldn't take any more messages.
    

Problem conclusion

  • NMQI code is modified such that the locking mechanism at client
    is more strict on the message indexing while streaming messages
    from the queue manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.11
    --------           --------------------
    Windows            7.0.1.11
    
                       v7.1
    Platform           Fix Pack 7.1.0.4
    --------           --------------------
    Windows            7.1.0.4
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.3
    
    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

    IV37602

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-05

  • Closed date

    2013-05-16

  • Last modified date

    2013-05-16

  • 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 AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R701 PSY

       UP

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

Document Information

Modified date:
16 May 2013