APAR status
Closed as program error.
Error description
In IBM MQ Managed .NET client application intermittently fails with errors 2195 and 2009 when attempting to connect to a queue manager. The traces show the following: 0007169B 10:43:58.677585 11868.18 System.NotSupportedException: The BeginWrite method cannot be called when another write operation is pending. at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback asyncCallback, Object asyncState) at IBM.WMQ.Nmqi.MQEncryptedSocket.Write(Byte[] buffer, Int32 offset, Int32 length) 0007169C 10:43:58.677585 11868.18 ----------} MQEncryptedSocket.Write(byte[], int, int) rc=OK 0007169D 10:43:58.677585 11868.18 Send << - n = 0 0007169E 10:43:58.677585 11868.18 System.NotSupportedException: The BeginWrite method cannot be called when another write operation is pending. at System.Net.Security._SslStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback asyncCallback, Object asyncState) at IBM.WMQ.Nmqi.MQEncryptedSocket.Write(Byte[] buffer, Int32 offset, Int32 length) at IBM.WMQ.MQTCPConnection.Send(Byte[] bytes, Int32 offset, Int32 length, Int32 segmentType, Int32 tshType) 0007169F 10:43:58.693209 11868.18 New MQException CompCode: 2 Reason: 2195 000716A0 10:43:58.693209 11868.18 New NmqiException CompCode: 2 Reason: ... 00716DF 10:43:58.708837 11868.5 CompCode: 2, Reason: 2009 000716E0 10:43:58.708837 11868.5 New MQException CompCode: 2 Reason: 2009 CompCode: 2 Reason: 2009
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users using a multi-threaded MQ managed .Net client application. Platforms affected: Windows, Linux on x86-64 **************************************************************** PROBLEM DESCRIPTION: When using MQ managed .Net client in multi-threading, a timing issue caused the exception System.NotSupportedException when trying to write on the socket.
Problem conclusion
MQ managed .Net client code has been corrected so that the timing issue doens't cause exception System.NotSupportedException. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.3 LTS 9.3.0.15 v9.x CD 9.3.5 The latest available maintenance can be obtained from 'IBM MQ Recommended Fixes' https://www.ibm.com/support/pages/recommended-fixes-ibm-mq If the maintenance level is not yet available information on its planned availability can be found in 'IBM MQ Planned Maintenance Release Dates' https://www.ibm.com/support/pages/ibm-mq-planned-maintenance-rel ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT43410
Reported component name
MQ APPLIANCE M2
Reported component ID
5900ALJ00
Reported release
930
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-03-22
Closed date
2023-11-24
Last modified date
2023-11-24
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
MQ APPLIANCE M2
Fixed component ID
5900ALJ00
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
04 December 2023