IT22461: TIMEOUTNOTIFICATION NODE MAY DELAY SENDING SOME EVENTS AFTER AN MQSIRELOAD COMMAND

APAR status

• Closed as program error.

Error description

• A TimeoutNotification node is processing and sending
  notification messages for a Timeout request.
  
  A new Timeout request message is received with the
  'AllowOverwrite' value set to 'true'.
  
  However the TimeoutNotification node may continue sending
  timeout notifications related to the previous Timeout request
  for the same Timeout identifier, before changing over to the new
  Timeout request message settings.
  
  In this case the TimeoutNotification node is expected to ignore
  the previous Timeout request message and should start processing
  the new Timeout request message immediately.
  
  The problem is more likely to occur after an Integration Server
  restart or reload, when the 'IgnoreMissed' property of the
  existing Timeout request is set to 'False'.
  
  In this scenario, if a new Timeout request arrives while the
  TimeoutNotification node is still processing missed timeouts
  from the restart or reload, then  a duplicate Timeout request
  message may be put to the SYSTEM.BROKER.TIMEOUT.QUEUE for the
  same Timeout Identifier.
  
  Additional Symptom(s) Search Keyword(s):TimeoutNotification,
  Controlled mode, timeout intervals, timeouts, TimeoutControl
  

Local fix

• The problem is reduced, to some extent, if control events
  created by the TimeoutControl with short timeout intervals, are
  prioritised ahead of events which have longer timeout intervals.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise v11.0 and IBM
  Integration Bus v10 using the TimeoutNotification node.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A TimeoutNotification node is processing and sending
  notification messages for a Timeout request.
  
  A new Timeout request message is received with the
  'AllowOverwrite' value set to 'true'.
  
  However the TimeoutNotification node may continue sending
  timeout notifications related to the previous Timeout request
  for the same Timeout identifier, before changing over to the new
  Timeout request message settings.
  
  In this case the TimeoutNotification node is expected to ignore
  the previous Timeout request message and should start processing
  the new Timeout request message immediately.
  
  The problem is more likely to occur after an Integration Server
  restart or reload, when the 'IgnoreMissed' property of the
  existing Timeout request is set to 'False'.
  
  In this scenario, if a new Timeout request arrives while the
  TimeoutNotification node is still processing missed timeouts
  from the restart or reload, then  a duplicate Timeout request
  message may be put to the SYSTEM.BROKER.TIMEOUT.QUEUE for the
  same Timeout Identifier.
  

Problem conclusion

• The product now prevents delays in sending a timeout
  notification for a new Timeout request  after a reload or
  restart of an Integration Server.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.13
  v11.0      11.0.0.1
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels