IV75816: WEBSPHERE MQ 7.1 .NET CLIENT (USING XMS) TRIES TO RE-CONNECT AND GETS A CWSIT0006E EXCEPTION

APAR status

• Closed as program error.

Error description

• Re-create:
  Stop a WebSphere Enterprise Service Bus completely for 15-20
  minutes. Once it is restarted .Net client is not able to
  connect automatically
  
  In this case it was a Windows Visual Basic .NET applications
  using IBM XMS to talk to WebSphere SIBus queues.
  
  The following exception is seen-
  
  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 DispatcherLib.XMSHelper.MakeConnection(String endPoints,
  String busName, String username, String password)
     at DispatcherLib.WESBReader.InitializeConsumer()
     at DispatcherLib.WESBReader.DoWork()
  
  Linked Exception : IBM.XMS.Core.SIResourceException:
  CWSIT0006E: It is
  not possible to connect to bus nnnnnnnn.
  .
  .
  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.
     at IBM.XMS.SIB.Trm.TrmSICoreConnectionFactoryImpl.Bootstrap
  (Credentials credentials, SICoreConnectionProperties
  connectionProperties, ClientAttachProperties cap)
     at
  IBM.XMS.SIB.Trm.TrmSICoreConnectionFactoryImpl.CreateConnection
  (Credentials credentials, SICoreConnectionProperties
  connectionProperties)
     at
  IBM.XMS.SIB.Trm.TrmSICoreConnectionFactory.CreateConnection
  (String username, String password, SICoreConnectionProperties
  connectionProperties)
     at IBM.XMS.Impl.ConnectionFactory.CreateConnection(String
  userName,
  String password)
  

Local fix

• Restart the .NET application
  

Problem summary

• XMSv2.1 Application TRYING TO RE-CONNECT
  TO WAS THROWS CWSIT0006E EXCEPTION
  

Problem conclusion

• CloseConversation is called once the application connection
  breaks. Prior to the fix the main connection is closed using the
  refCount which is wrong.The Connection should be closed using
  the conversation count rather.
  

Temporary fix

Comments

APAR Information

• 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

  MSG SRVCS CL .N

• Fixed component ID

  5724M2100

Applicable component levels

• R210 PSY

     UP