IBM Support

IT19182: MQ DOT NET MANAGED CLIENT CONNECTION ONLY ATTEMPTS CONNECTION TOFIRST HOST IN CONNECTION NAMELIST

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

  • When connecting in managed mode, the application attempts to
    connect to the first connection defined in the CCDT.  If that
    connection  is not  reachable, the following exception is seen
    in MQ  trace:
    
    System.Net.Sockets.SocketException (0x80004005): No connection
     could be  made because the target machine actively refused it
            1.2.3.4:1414
       at System.Net.Sockets.Socket.DoConnect(EndPoint
    endPointSnapshot, SocketAddress socketAddress)
       at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
       at
    IBM.WMQ.MQTCPConnection.ConnectUsingLocalAddr(ParsedLocalAddr
    localAddr, IPAddress ipad, Int32 port)
    However, no attempt is made to connect to the other connection
    name defined in the CCDT.  The following is also reported in
    the trace:
    AMQ9202: Remote host
    '1.2.3.4(1414),5.6.7.8(1415),9.10.11.12(1416),
    13.14.15.16(1417)' not available, retry later.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    MQ .NET managed connection client users who try to connect queue
    managers with multiple connection names specified in the CONNAME
    attribute of the client connection channel
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When multiple connection names were passed in the CONNAME
    parameter of the channel, the MQ .NET client was attempting to
    connect to the first connection name. If the first connection
    name was not reachable, a logic error meant that it did not
    subsequently attempt to connect using any other connection name
    specified in the CONNAME parameter.
    

Problem conclusion

  • The MQ .NET managed connection client code has been modified to
    attempt a connection to each entry in the CONNAME, in the order
    specified, until either a successful connection is established,
    or the end of the list is reached.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.3
    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

    IT19182

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-08

  • Closed date

    2017-04-28

  • Last modified date

    2017-04-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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

  • R900 PSY

       UP

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

Document Information

Modified date:
28 April 2017