IT29492: OUTBOUND BAPI SCENARIOS DO NOT SCALE WELL UNDER HIGH LATENCY CONDITIONS.

APAR status

• Closed as program error.

Error description

• When using the SAPRequest Node to make BAPI calls the adapter
  un-necesarily issues a spculative "ping" call to the connection
  when obtaining a connection from the pool.
  .
  Since this operation occurs under a lock, if the time taken to
  complete the ping call is high, for example when the SAP system
  is on a different cloud / data center. Then this can result in a
  transaction rate ceiling that can not be addressed by adding
  more instances of the message flow.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus version 10 or App conect
  Enterprise version 11 using the SAPRequest Node.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <span style="background-color:rgb(255, 255, 255)">When using the
  SAPRequest Node to make BAPI calls the adapter  </span><span
  style="background-color:rgb(255, 255, 255)">makes unnecessary
  speculative "ping" call to the connection </span><span
  style="background-color:rgb(255, 255, 255)">when obtaining a
  connection from the pool.                     </span>
  <span style="background-color:rgb(255, 255, 255)">
  
  </span>
  <span style="background-color:rgb(255, 255, 255)">Since this
  operation occurs under a lock, if the time taken to </span><span
  style="background-color:rgb(255, 255, 255)">complete the ping
  call is high, for example when the SAP system </span><span
  style="background-color:rgb(255, 255, 255)">is on a different
  cloud / data center. Then this can result in a ceiling on the
  </span><span style="background-color:rgb(255, 255,
  255)">transactional throughput that can not be addressed by
  adding </span><span style="background-color:rgb(255, 255,
  255)">more instances of the message flow.
                             </span>
  

Problem conclusion

• The speculative ping operation has been removed.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.19
  v11.0      11.0.0.7
  
  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