Outbound Requests Using SES ApplicationContainer CONTAINERURL Fail with 'Status Code - 404'(SBL-EAI-04117) in Versions 21.2 to 21.7 (Doc ID 2774246.1)

Last updated on APRIL 10, 2023

Applies to:

Siebel CRM - Version 21.2 to 21.7 [Release V17]
Information in this document applies to any platform.

Symptoms

On : 21.4 version, Siebel EAI

Any attempt to use the CONTAINERURL to invoke outbound calls fail with HTTP-404 (not found)

CONTAINERURL is used by :

Outbound Web Services - Unix/Linux only
Outbound REST - All platforms
Java Business Services (JBS) - All platforms
- JMS - All platforms
- Siebel Test Automation Framework - All platforms
- The new Email Response 64bit driver for IMAP and POP3 (using JavaMail option) ONLY.

Please refer to this KM article for more information on the SES applicationcontainer usage:

• Which Siebel EAI Integration Functionality Uses The ApplicationContainer Tomcat During Inbound And Outbound Service Calls? (Doc ID 2441695.1)

And any call to functionality that uses SES CONTAINERURL leads to HTTP 404

E.g: Any call to any outbound web service on Linux would lead to :

object manager log:

EAITransport EAITransportDebug 4 0000047c609056e8:0 2021-05-04 10:10:08 *** HTTP response Headers from Data Send request:

HTTP/1.1 404

ObjMgrLog Error 1 0000047c609056e8:0 2021-05-04 10:10:08 (httptransport.cpp (1153)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 404'

catalina.out

05-May-2021 12:38:13.685 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Connector] failed to set property [SSLEngine] to [on]

05-May-2021 12:38:13.752 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path:
(...)
2021-05-05 12:38:22,904 main ERROR Servlet contains invalid attributes "fileName", "type"
(...)

05-May-2021 12:38:23.008 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
(...)
05-May-2021 12:38:59.986 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/siebel] startup failed due to previous errors

localhost.<date>.log

05-May-2021 11:22:30.425 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.siebel.opcgw.cloudgateway.CGServletContext]

java.lang.NumberFormatException: For input string: "$tlslistnerport"

Note: There is also a related defect affecting Siebel Management Console (SMC) leading to HTTP-404 when deploying changes to Servers, accessible through this link.