App Connect

 View Only
Expand all | Collapse all

No Timeout Trigger from Http Input node in REST API : ACE 12

  • 1.  No Timeout Trigger from Http Input node in REST API : ACE 12

    Posted Fri May 27, 2022 12:05 PM
    Hi,

    I've come across a Timeout problem in Rest API.

    I created a REST API by importing the OpenAPI Document and Created the Subflow for the operation and and enabled all the Error Handling Subflows in which I have placed compute nodes to prepare the custom error response for Failure, Catch and Timeout activity.

    Input Message Type: JSON

    My Subflow for the Operation (Post Call):

    Input Node --> Compute Node -->MQOutput Node
    MQInput Node -->Compute Node  --> OutputNode

    Deployed into an Independent Integration Server.

    I've set the Http Timeout as 30 Seconds in the Rest API Message Flow and there on the expectations is that once the REST API is invoked right after 30 seconds is passed the Timeout Terminal will trigger the message and there it will pass it to the timeout handler subflow, prepare the custom message and pass it to the requestor as response.

    Problem:

    The above scenario is not happening rather than a Validation Error is being thrown from HttpInput Node and handled by the Failure Sublow after 30 Seconds.

    As I enable the User Trace,

    This is the Message I could see :

    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xml="http://www.w3.org/XML/1998/namespace">
    <SOAP-ENV:Body>
    <SOAP-ENV:Fault>
    <SOAP-ENV:Code>
    <SOAP-ENV:Value>SOAP-ENV:Sender</SOAP-ENV:Value>
    <SOAP-ENV:Subcode>
    <SOAP-ENV:Value/>
    </SOAP-ENV:Subcode>
    </SOAP-ENV:Code>
    <SOAP-ENV:Reason>
    <SOAP-ENV:Text xml:lang="en">A timeout occurred during processing</SOAP-ENV:Text>
    </SOAP-ENV:Reason>
    <SOAP-ENV:Node>http://192.168.1.2:7802/v1/sample/example</SOAP-ENV:Node>
    <SOAP-ENV:Detail>
    <text>Timeout. The Broker integration_server did not provide a response within the specified time interval (30 seconds). The message reached the main flow, but timed out during processing. It was then given to the timeout flow for processing.</text>
    </SOAP-ENV:Detail>
    </SOAP-ENV:Fault>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>


    How to resolve this issue? I want the trigger from timeout terminal to prepare my custom message

    ------------------------------
    TARANDEEP JANDU
    ------------------------------


  • 2.  RE: No Timeout Trigger from Http Input node in REST API : ACE 12

    Posted Fri July 08, 2022 12:27 PM
    The timeout subflow is only used if you are using the embedded integration server listener.  If using the node level shared listener (default for the REST APIs), the listener handles the timeouts.  The error message you provided suggests that you are using the shared listener and thus your timeout subflow will be ignored.  If you look at the syslog during the deploy action, it usually outputs a message stating the timeout terminal is connected and will be ignored.  You can resolve this by switching to the embedded listener.

    ------------------------------
    MATTHEW SEGALL
    ------------------------------