IT45467: AFTER APPLYING IT34468 AN INLINE HTTP RETRY MAY BE OBSERVED WHENA BACKEND SERVICE TIMES OUT

APAR status

• Closed as program error.

Error description

• Under APAR IT34468 the capability to recover from broken
  connections was introduced to the HTTP, SOAP and REST request
  nodes such that if there was a failure writing to the remote
  server because the connection had been broken or  the backend
  server did not reply then a single retry would be issued inline
  so that a flow could recover from transient failures. This retry
  would  only occur if the timeout for the  request had not yet
  passed and the time out for the second request would be reduced
  to take into account the elapsed time of the first request.
  
  However, if the timeout for the request is overridden by the
  local environment property Destination.HTTP.Timeout to a value
  smaller than on the node property then the  second request will
  be sent as long as the timeout based on the node property has
  not been exceeded.
  
  The retry behaviour can be disabled entirely  using the env var
  MQSI_HTTP_REQUEST_NODE_NO_RETRY
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise version 12.0.12.0 or
  higher using the HTTP, SOAP or REST request nodes.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Under APAR IT34468 the capability to recover from broken
  connections was introduced to the HTTP, SOAP and REST request
  nodes such that if there was a failure writing to the remote
  server because the connection had been broken or  the backend
  server did not reply then a single retry would be issued inline
  so that a flow could recover from transient failures.
  
  This retry would only occur if the timeout for the  request had
  not yet passed and the time out for the second request would be
  reduced to take into account the elapsed time of the first
  request.
  
  However, if the timeout for the request is overridden by the
  local environment property Destination.HTTP.Timeout to a value
  smaller than on the node property then the  second request will
  be sent as long as the timeout based on the node property has
  not been exceeded.
  
  The retry behaviour can be disabled entirely  using the env var
  MQSI_HTTP_REQUEST_NODE_NO_RETRY however this environment
  variable does not function when set in server.conf.yaml. The env
  var fuinctions correctly if set in the local shell environment.
  

Problem conclusion

• The eligibility for an inline retry now takes account of the
  Destination.HTTP.Timeout LocalEnvironment override.
  
  MQSI_HTTP_REQUEST_NODE_NO_RETRY now functions correctly when set
  in the EnvironmentVariables section of the server.conf.yaml
  file.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v12.0      12.0.12.0
  
  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

  APP CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels