IT36612: SOAPASYNCRESPONSE NODE SHOULD CREATE HTTPINPUTHEADER WHEN NOT USING 'HTTP ASYNCHRONOUS REQUEST-RESPONSE' PROPERTY

APAR status

• Closed as program error.

Error description

• In ACE V11, when SOAPAsyncRequest and SOAPAsyncResponse nodes
  are used in the default mode, which is to use WS-Addressing to
  call the paired SOAPAsyncResponse node, an HTTPInputHeader is
  expected from SOAPAsyncResponde node. However, the
  SOAPAsyncResponse node propagates out a HTTPResponseHeader.
  This can cause a failure when the node is connected to a
  Collector node and may result in BIP3159S and BIP6105E errors.
  
  
  In its default mode, the backend makes a webservice call to
  the SOAPASyncResponse node's endpoint. Accordingly a
  HTTPInputHeader is expected. However, if using 'HTTP
  asynchronous request-response' property, the HTTP Request
  socket is used to receive the response and hence
  HTTPResponseHeader is expected.
  
  The HTTPInputHeader needs
  'X-Original-HTTP-Command' property. Similarly, the
  HTTPResponseHeader needs 'X-Original-HTTP-Status-Line'. If
  those fields are missing it can cause failures when the tree is
  reconstructed from a serialized bitstream, which is the reason
  it throws errors when used with the Collector node.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All Users of IBM App Connect Enterprise V11.0 with
  SoapAsynRequest and SoapAsyncResponse nodes.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  In App Connect Enterprise V11, when SOAPAsyncRequest and
  SOAPAsyncResponse nodes are used in the default mode, which is
  to use WS-Addressing to call the paired SOAPAsyncResponse node,
  an HTTPInputHeader is expected from SOAPAsyncResponde node.
  However, the SOAPAsyncResponse node propagates out an
  HTTPResponseHeader. This can cause a failure when the node is
  connected to a Collector node and may result in BIP3159S and
  BIP6105E errors.
  
  In its default mode, the backend makes a webservice call to the
  SOAPAsyncResponse node's endpoint. Accordingly, an
  HTTPInputHeader is expected. However, if using 'HTTP
  asynchronous request-response' property, the HTTP Request socket
  is used to receive the response and hence HTTPResponseHeader is
  expected. But in both cases, HTTPResponseHeader is seen
  propagated out from SOAPAsyncResponse node.
  
  The HTTPInputHeader needs 'X-Original-HTTP-Command' property.
  Similarly, the HTTPResponseHeader needs
  'X-Original-HTTP-Status-Line'. If those fields are missing it
  can cause failures when the tree is reconstructed from a
  serialized bitstream, which is the reason it throws errors when
  used with the Collector node.
  

Problem conclusion

• The SOAPAsyncResponse node is corrected to propagate
  HTTPInputHeader when used in the default ws-addressing mode.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.13
  v12.0      12.0.2.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