IT37733: MFT agent monitorGroupRetryLimit is not working as expected because monitor execution count is not getting updated

APAR status

• Closed as program error.

Error description

• When monitorMaxResourcesInPoll was set to a value greater than
  or equal to 1, the worker thread will be used to scan messages
  during the monitor poll.
  While using worker threads the executionCount which indicates
  the number of times a MonitorResourceGroupItem has been executed
  for an agents life time, was not getting updated.
  This resulted in executionCount being 0 which indicates that the
  polling has not happened.
  So any MonitorResourceGroupItem found during the scan will
  always be included in the transfer. This resulted in
  monitorGroupRetryLimit property not working as expected.
  

Local fix

• Setting monitorMaxResourcesInPoll=-1 (default value) in the
  agent.properties file will allow the monitorGroupRetryLimit to
  work as expected.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  IBM MQ MFT users using MFT resource monitor
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When monitorMaxResourcesInPoll was set to a value greater than
  or equal to 1, the worker thread will be used to scan messages
  during the monitor poll.
  While using worker threads the executionCount which indicates
  the number of times a MonitorResourceGroupItem has been executed
  for an agents life time, was not getting updated.
  This resulted in executionCount being 0 which indicates that the
  polling has not happened.
  So any MonitorResourceGroupItem found during the scan will
  always be included in the transfer. This resulted in
  monitorGroupRetryLimit property not working as expected.
  

Problem conclusion

• IBM MQ MFT resource monitor has been updated such that
  executionCount gets updated when worker threads are used to scan
  monitor resource.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.5
  v9.x CD    9.2.5
  
  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

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels