IBM Support

IT07027: SECURITY EXIT REQUEST TO 'MQXCC_SEND_AND_REQUEST_SEC_MSG' FLOW CAUSES CHANNEL TERMINATION WHEN USING MANAGED .NET APPLICATION

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

  • An attempt to connect to a queue manager with a server side
    channel security exit is made by a .NET Client application with
    no client side exit. The .NET Client application reports
    IBM.WMQ.Nmqi.NmqiException and causes the channel to close.
    .
    Client trace shows:
    IBM.WMQ.Nmqi.MQRcvThread (04)--- X IBM.WMQ.Nmqi.NmqiException:
    Exception of type 'IBM.WMQ.Nmqi.NmqiException' was thrown.
       at IBM.WMQ.Nmqi.MQRcvThread.ReceiveBuffer()
     .
     IBM.WMQ.MQTCPConnection (05)---- >
    AsyncFailureNotify(NmqiException,Boolean) entry
    [IBM.WMQ.Nmqi.NmqiException: Exception of type
    'IBM.WMQ.Nmqi.NmqiException' was thrown.
       at IBM.WMQ.Nmqi.MQRcvThread.ReceiveBuffer()
    .
    MQ error logs shows:
     AMQ9552: Security flow not received.
     EXPLANATION:
     During communications through channel 'XXXXX' the local
    security exit requested security data from the remote machine.
    The security data has not been received so the channel has been
    closed.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ XMS (Message Service Client
    for .NET) and the MQ .NET Managed client that have a security
    exit defined on the queue manager side of a channel which
    returns an exit response of MQXCC_SEND_AND_REQUEST_SEC_MSG and
    no security exit defined on the client side of the channel.
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The NMQI client code was incorrectly sending a user ID (UID)
    flow rather than a security flow in response to the security
    exit's
    MQXCC_SEND_AND_REQUEST_SEC_MSG request.
    

Problem conclusion

  • The MQ XMS (Message Service Client for .NET) and the MQ .NET
    Managed client code has been modified to respond correctly to
    MQXCC_SEND_AND_REQUEST_SEC_MSG with a null security flow, rather
    than a UID flow.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.14
    v7.1       7.1.0.7
    v7.5       7.5.0.6
    v8.0       8.0.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

    IT07027

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-02-09

  • Closed date

    2015-04-30

  • Last modified date

    2015-04-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 WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 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","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 April 2015