IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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

Temporary fix

Comments

APAR Information

  • APAR number

    IT29492

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-19

  • Closed date

    2019-12-18

  • Last modified date

    2019-12-18

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 December 2019