IBM Support

IJ00085: IBM MQ XMS Client connecting to WAS SIBUS hangs intermittently

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

  • XMS.NET Client application connecting to WAS SIBus hangs
    intermittently while creating a connection.Following exception
    is thrown after couple of hours
    
    22.08.2017 12:31:07 - ERROR - XMS-Fehler EC='CWSIA0241'
    IBM.XMS.XMSException - EXCEPTION_RECEIVED_CWSIA0241
    EXCEPTION_RECEIVED_CWSIA0241.explanation
    EXCEPTION_RECEIVED_CWSIA0241.useraction
       at IBM.XMS.Impl.ConnectionFactory.CreateConnection(String
    userName,
         String password)
       at IBM.XMS.Impl.ConnectionFactory.CreateConnection()
       at IBM.Module.ISH.Interface.XmsClient.connect()
       at IBM.Module.ISH.Interface.XmsClient.read()
       at IBM.Module.ISH.Interface.IshXmsProxy.read(Param
    queueCorrelationInfo, Param queueInfo)
    22.08.2017 12:31:07 - ERROR - LinkedException (XMSException):
    IBM.XMS.Core.SIResourceException - CWSIT0006E: It is not
    possible to
    connect to bus ISH.MQClientLinkProxy.Bus because the following
    bootstrap
    servers could not be contacted
    192.168.170.18:7276:BootstrapBasicMessaging and the following
    bootstrap
    servers returned an error condition . See previous messages for
    the
    reason for each bootstrap server failure.
    The client cannot connect to the bus. This situation may be due
    to
    configuration problems, network problems or it may be that none
    of the
    required bootstrap servers or messaging engines are currently
    available.
    Ensure that the network is working correctly and that the
    required
    bootstrap servers and messaging engines are available.
       at
    IBM.XMS.SIB.Trm.TrmSICoreConnectionFactoryImpl.Bootstrap(Credent
    ials
    credentials, SICoreConnectionProperties connectionProperties,
    ClientAttachProperties cap)
       at
    IBM.XMS.SIB.Trm.TrmSICoreConnectionFactoryImpl.CreateConnection(
    Credenti
    als credentials, SICoreConnectionProperties
    connectionProperties)
       at
    IBM.XMS.SIB.Trm.TrmSICoreConnectionFactory.CreateConnection(Stri
    ng
    username, String password, SICoreConnectionProperties
    connectionProperties)
       at IBM.XMS.Impl.ConnectionFactory.CreateConnection(String
    userName,
    String password)
    IBM.XMS.Core.SIConnectionLostException - Exception of type
    'IBM.XMS.Core.SIConnectionLostException' was thrown.
       at
    IBM.XMS.SIB.Comms.Client.ClientSideConnection.Connect(Connection
    Properti
    es cp, IClientComponentHandshake cch, SICoreConnectionProperties
    siProps)
       at
    IBM.XMS.SIB.Trm.TrmSICoreConnectionFactoryImpl.Bootstrap(Credent
    ials
    credentials, SICoreConnectionProperties connectionProperties,
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    XMS.NET Applications connecting to WAS SIBus
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When creating  a connection to WAS SIBus,XMS.NET application
    hangs intermittently.
    

Problem conclusion

  • While creating a connection to WAS SIBus,XMS.NET assigns a
    conversationId to each connection and adds into the hashtable
    for future reference.While adding the conversationId into the
    hashtable,the threads have to be synchronized which wasn't the
    case,due to which there was an intermittent hang while creating
    a connection.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 LTS   9.0.0.4
    
    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

    IJ00085

  • Reported component name

    WMQ XMS V 8.0

  • Reported component ID

    5724H7257

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-18

  • Closed date

    2018-03-29

  • Last modified date

    2018-04-10

  • 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 XMS V 8.0

  • Fixed component ID

    5724H7257

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":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 April 2018