IT19674: HTTPINPUT NODE PROPAGATES A HTML TIMEOUT FAULT WITH A MISSING END TAG

APAR status

• Closed as program error.

Error description

• If a HTTPInput node does not receive a HTTP reply by the time
  the HTTP client timeout is reached, a fault message will be
  propagated to the timeout terminal in the fault format selected
  on the HTTPInput node.
  
  When the HTTP fault format is HTML (or in the case of REST APIs
  where the format is fixed as HTML irrespective of what the user
  selects on the HTTPInput node in the generated flow) a HTML
  timeout message will be propagated to the timeout terminal.  If
  an attempt is made to parse this HTML message with the XMLNSC
  parser this will fail because a </hr> tag is missing.  While it
  is not guaranteed that HTML can be parsed by an XML parser an
  IIB message flow should be able to parse its own HTML fault
  message.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10.0 setting the fault format
  on the HTTPInput node to HTML or using a deployable REST API and
  parsing the timeout fault message
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A HTTPInput node has a timeout terminal that can be propagated
  to when the integration server embedded listener is used. If a
  HTTP reply has not been sent by the time the HTTP client timeout
  is reached, a fault message will be propagated to the timeout
  terminal. The fault message is either HTML, SOAP 1.1 or SOAP 1.2
  based on the fault format selected on the HTTPInput node; except
  in the case of deployable REST APIs where the format is fixed as
  HTML irrespective of what the user selects on the HTTPInput node
  in the generated flow.
  
  When a HTML timeout message is propagated to the timeout
  terminal and the message is parsed with the XMLNSC parser, this
  fails because a </hr> tag is missing. While it is not guaranteed
  that HTML can be parsed by an XML parser an IIB message flow
  should be able to parse its own HTML fault message.
  

Problem conclusion

• The HTML fault format propagated from the HTTPInput node's
  timeout terminal now has the missing </hr> tag and can be
  successfully parsed by the XMLNSC parser.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.9
  
  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

• RA00 PSY

     UP