IT33752: DOC UPDATE : MAXIMUM MESSAGE RATE VALUE IS NOT DIVIDED EQUALLY AMONG ALL THREADS OF A MESSAGE FLOW

APAR status

• Closed as documentation error.

Error description

• KnowledgeCenter page bj58270_.html incorrectly says
  'maximumRateMsgsPerSec'  value is divided equally among all
  threads that are running in the message flow.
  ---
  The maximum message rate value is divided equally among all
  threads that are running in the message flow irrespective of the
  number of input nodes within the flow to achieve the configured
  maximumRateMsgsPerSec.
  ---
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM AppConnect Enterprise V11.0 and IBM Integration
  Bus V10.0 using the maximumRateMsgsPerSec property.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  KnowledgeCenter page bj58270_.html incorrectly says
  'maximumRateMsgsPerSec'  value is divided equally among all
  threads that are running in the message flow.
  

Problem conclusion

• The following paragraph in product Knowledge Center page
  bj58270_ will be updated  :
  
  From :
  
  "The system administrator is able to restrict the rate that an
  individual message flow can run at by setting the maximum rate
  property. The maximum rate is specified as the total number of
  input messages processed every second. The maximum rate value is
  divided equally among all threads that are running in the
  message flow irrespective of the number of input nodes within
  the flow."
  
  To :
  
  "The system administrator is able to restrict the rate that an
  individual message flow can run at by setting the maximum rate
  property. The maximum rate is specified as the total number of
  input messages processed every second by all the threads that
  are running in the message flow."
  
  Following example  will also be removed from the documentation
  as it incorrectly describes the product functionality.
  -------------<p>The following three examples assume the maximum
  rate is set to 50, and helps to highlight some of the variations
  that can occur from basic to more complex
  scenarios:</p><ul><li>A message flow has one input node with no
  additional instances:<ul><li>Only a single thread in
  operation.</li><li>The full maximum rate allocation of 50
  messages every second is applied to that one
  thread.</li></ul></li><li>A message flow has one input node with
  one additional instance:<ul><li>Two threads in operation. One
  for the node and one for the additional instance.</li><li>The
  maximum rate is split equally across the two threads. Each
  thread has a maximum rate allocation of 25 messages every
  second.</li></ul></li><li>A message flow has three input nodes
  with four additional instances that are specified on the first
  node and three additional instances that are specified on the
  second node:<ul><li>10 threads in operation. Three input node
  threads, four additional instance threads for the first node,
  and three additional instance threads for the second
  node.</li><li>The maximum rate is split equally across the 10
  threads. Each thread has a maximum rate allocation of five
  messages every second.</li></ul></li></ul>-----------------
  

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

Applicable component levels