IT16167: Managed .NET client application does not send heartbeat request to queue manager

APAR status

• Closed as program error.

Error description

• When using an IBM MQ managed .Net client application, it is
  observed that a heartbeat flow is received from the queue
  manager every 'HBINT + 5 seconds', but no heartbeat
  communication is initiated from the client side.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  MQ users using a managed .NET client application to connect to
  the Queue Manager
  
  
  Platforms affected:
  Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A logic error in the MQ managed .NET client code meant that the
  client did not send a heartbeat request to the queue manager in
  the expected circumstances.
  

Problem conclusion

• The MQ managed .NET client logic has been corrected such that
  the heartbeat request is sent when expected by the MQ protocol.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.10
  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 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 BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels