APAR status
Closed as program error.
Error description
If the number of connections to WAS Service Integration Bus reach maximum limit i.e 65536, XMS.NET Client application throws an unhandled CWSIT0006E exception which causes the application to abruptly end.Following is the exception 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.
Local fix
Create one connection and use the same for any subsequent operations.
Problem summary
**************************************************************** USERS AFFECTED: XMS.NET applications creating 65536 connections to WAS Service Integration Bus Platforms affected: Windows **************************************************************** PROBLEM DESCRIPTION: If a XMS .NET application creates 65536 connections to WAS Service Integration Bus an unhandled exception is thrown by XMS.NET and the only way to recover was to re-start the application.
Problem conclusion
If the number of connections to WAS Service Integration Bus reach the maximum limit i.e 65536, XMS.NET should throw an exception which can be handled by the client application. --------------------------------------------------------------- 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
IJ01244
Reported component name
IBM MQ XMS V 8.
Reported component ID
5724H7257
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-02
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
IBM MQ XMS V 8.
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":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 April 2018