IT32606: MQ .Net core application takes several seconds to re-establish aconnection with a queue manager after a failover

APAR status

• Closed as program error.

Error description

• XMS Managed .NET core application takes up to 4 seconds to
  connect to the queue manager after a failover with multiple
  connection name.
  
  Example: hostname1(1234),hostname2(1235) are connection name
  used.
  
  When hostname1 fails and switched to hostname2 then several
  seconds of delay is observed when trying to connect to
  hostname2.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using XMS managed .NET core application with multiple
  connection names to connect to queue manager. Multiple
  connection names when set in CCDT is also affected.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A logic error caused delays when using multiple connection names
  for reconnection, due to unnecessary additional operations when
  the connection name list was processed.
  

Problem conclusion

• The XMS Managed .NET core code has been corrected to improve the
  performance when multiple connection names are used
  

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

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels