IBM Support

IT28500: FDC with Probe Id RM680065 and AMQ9504E Error are reported when a Java or managed .NET client issues an object inquiry

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

  • A Java or managed .NET client application receives
    MQRC_CONNECTION_BROKEN when it connects to a V9.1 Queue Manager.
    The same application would function normally when connecting to
    a Queue Manager at a level lower than MQ V9.1
    
    On the MQ Server, a failure data capture (FDC) record is
    generated, with the following Probe Id, Component, and Function
    Stack:
    
    Probe Id          :- RM680065
    Component         :- rriBadDataReceived
    Program Name      :- amqrmppa
    Major Errorcode   :- rrcE_PROTOCOL_ERROR
    Probe Description :- AMQ9504E: A protocol error was detected for
                         channel 'Channel_Name'.
    Arith1            :- 125 (0x7d)
    Arith2            :- 116 (0x74)
    Comment1          :- Channel_Name
    
    The error occurs when the application sends an MQINQ call where
    the provided IntAttrCount parameter is greater than the provided
    SelectorCount parameter.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Java and fully managed .NET clients that call inquire() or
    MQINQ() methods are potentially affected, based on the
    parameters passed.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The MQ 9.1 SVRCONN channel agent incorrectly produces a protocol
    error FDC record if the passed IntAttrCount parameter is greater
    than the passed SelectorCount parameter, in previous releases
    the SVRCONN agent would attempt to process the inquiry request.
    

Problem conclusion

  • The code has been updated so that the inquiry request is
    processed the same as in previous releases of the MQ server.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 CD    9.1.3
    v9.1 LTS   9.1.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

    IT28500

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-18

  • Closed date

    2019-04-29

  • Last modified date

    2019-04-29

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 April 2019