IBM Support

IT43706: INTEGRATION NODE WIDE LISTENER CAN GIVE TIMEOUT RESPONSE UNDER HEAVY LOAD.

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

  • If HTTP Listener using flow is using  HTTP Request to invoke
    another HTTP Listener using flow then same thread allocation can
    lead do deadlock and hence timeout for first invoked HTTP
    Listener using flow.
    

Local fix

  • setting MaxKeepAliveRequests to 1 and increasing ListenerThreads
    to a value based on incoming request load might help.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users of App Connect Enterprise V12 using the Integration
    Node listener to execute web services flows which then make an
    inline call to another web service flow implemented on the same
    Integration Node.
    
    An example of an affected configuration would be:
    
    Flow 1
    HTTP Input Node (/flow1) -> HTTPRequestNode to (/flow2) -> HTTP
    Reply Node
    
    Flow 2
    <span style="background-color:rgb(255, 255, 255)">HTTP Input
    Node (/flow2)</span><span style="background-color:rgb(255, 255,
    255)"> </span><span style="background-color:rgb(255, 255,
    255)">-> HTTP Reply Node</span>
    
    Affected nodes include flows starting with HTTPInput or
    SOAPInput Nodes and making requests using any of the
    HTTPRequest, SOAPRequest, RESTRequest, HTTP Async Request, SOAP
    Async Request or REST Async Request Nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Requests to the second flow may timeout unexpectedly. The
    problem is caused by the listener scheduling work on the same
    thread which is waiting for a response from the first message
    flow in the scenario.
    

Problem conclusion

  • The Integration Node level listener has been modified such that
    work is no longer scheduled on threads which are waiting for a
    response.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v12.0      12.0.9.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 number

    IT43706

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0560

  • Reported release

    C00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-05-05

  • Closed date

    2023-06-28

  • Last modified date

    2023-06-28

  • 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

    5724J0560

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":"C00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 June 2023