IC70091: WHEN USING SHARECNV=0 ON WINDOWS, .NET CLIENT CONNECTIONS ARE LOCKED IN CLOSE-WAIT EVENTUALLY CONSUMING ALL AVAILABLE SOCKETS

WebSphere MQ V7.0 Fix Pack 7.0.1.4
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.4

APAR status

• Closed as program error.

Error description

• A WebSphere MQ .NET client connecting to a queue manager over a
  non-multiplexed channel does not close the socket after
  disconnecting from the queue manager. As a result, sockets are
  locked in CLOSE_WAIT state which can eventually result in no
  sockets being available for making further connections.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the WebSphere MQ .NET and XMS clients who use non-
  multiplexed (SHARECNV=0) channels to connect to queue managers.
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM SUMMARY:
  When a client makes a call to disconnect from the queue manager,
  it sends a MQDISC call to the queue manager. The queue manager
  acknowledges this and responds back to the client. Upon receipt
  of this response, the client must close the socket at its end to
  complete termination of the conversation. Since the client did
  not close the socket, all such sockets remained in CLOSE_WAIT
  state and therefore not being available for future connections.
  

Problem conclusion

• The WebSphere MQ .NET client code has been modified to ensure
  that the client side closes the socket after disconnecting from
  the queue manager.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.4
  --------           --------------------
  Windows            U200323
  
  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 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 WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R701 PSY

     UP