AI And EAI Connection Timeout Occurs And Inbound EAI Calls Return HTTP 408 Status Code When EAI Component Parameter "SISNAPI connection maximum idle time" (ConnIdleTime) Is Less Than 30 Seconds (Doc ID 2902124.1)

Last updated on MARCH 13, 2024

Applies to:

Symptoms

When an external system sends inbound REST calls into Siebel, it spawns off an EAI task, where the EAI task runs a SQL that takes 6+ minutes to run. The EAI log file shows the SQL did eventually complete and proceeded forwards to the next sequence of the execution.  The EAI task did not fail, did not error and did not time out.

However, while the SQL took 6+ minutes to run, the Siebel AI to EAI connection appears to have timed out, the AI localhost_access log shows an http 408 error code and roughly 30000 ms (30 seconds) execution time.

The following error message occurs in the localhost_access_log.<DATE>.txt file:

The behaviour occurs as follows:

1. Create an Inbound REST service on the Siebel application side.

The instructions from the following documentation was followed to perform initial configure/set up step:

a. Siebel Bookshelf > REST Guide > Chapter 4: Using the Siebel REST API:       https://docs.oracle.com/cd/F26413_14/books/RestAPI/using-the-siebel-rest-api.html#using-the-siebel-rest-api

b. MOS KM article:

• How To Test Siebel IP2016 and 17+ RESTFul Services API (Doc ID 2193144.2)

• How To Configure The IP17 Application Interface eai And eai_anon Applications For Inbound EAI And RESTFul API Integrations (Doc ID 2338945.2) > V. Testing the applications > b. Inbound RESTFul API

2. Launch SoapUI or Chrome Postman testing tool (or go to the external system's application) and send an inbound REST request into Siebel application. This works fine.

3. Submit an Inbound REST call which generates a SQL that takes 6+ minutes to run. This starts up an EAI task, the EAI task runs and shows the SQL completed in 6+ minutes, then continue with the next steps, etc. The EAI tasks did not fail, did not error and did not time out.

4. However, while the SQL took 6+ minutes to run, the AI to EAI connection appears to have timed out, the AI localhost_access log shows http 408 error code.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.