IBM Support

IT34468: SIMPLIFY HTTP RETRY

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 new function.

Error description

  • It is common for network connections to be terminated,
    especially in containers based solutions where backends may be
    elastically scaled to meet capacity. In this case it would
    improve the ability for flow to tolerate intermittent failure
    if the HTTPRequest node were able to make a single inline retry
    attempt if it encountered a broken connection when trying to
    write to a cached socket.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise V11.0 and V12.0 using
    HTTPRequest Nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">It is common
    for network connections to be terminated, </span><span
    style="background-color:rgb(255, 255, 255)">especially in
    containers based solutions where backends may be </span>
    <span style="background-color:rgb(255, 255, 255)">elastically
    scaled to meet capacity. In this case it would </span><span
    style="background-color:rgb(255, 255, 255)">improve the ability
    for flow to tolerate intermittent failure </span><span
    style="background-color:rgb(255, 255, 255)">if the HTTPRequest
    node were able to make a single inline retry </span><span
    style="background-color:rgb(255, 255, 255)">attempt if it
    encountered a broken connection when trying to </span><span
    style="background-color:rgb(255, 255, 255)">write to a cached
    socket.           </span>
    

Problem conclusion

  • If the HTTP Request node makes a request using a cached socket
    and it either fails to write to the socket or fails to read at
    least 1 byte from the socket then the HTTPRequest node will make
    another attempt using a new socket provided that no more than
    half of the allowed timeout has passed. The timeout for the
    second request is adjusted to take account of any time spent in
    the first attempt.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.20
    
    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 number

    IT34468

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-07

  • Closed date

    2022-10-07

  • Last modified date

    2022-10-07

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 October 2022