3336984 - 'Servlet.service() for servlet' and 'HTTP 500' errors in Cloud Integration

When making a call to your Cloud Integration/Integration Suite, the call fails with 'HTTP 500' which can be seen in the HTTP logs.

Also, when checking the Default traces/LJS logs of your Cloud Integration, an error in the class 'Servlet.service() for servlet' can be seen as the cause of the problem. Below, you can see examples of the error in the HTTP and LJS/default trace logs of your Cloud Integration:

HTTP:

• <IP> - - [<Timestamp>] "POST /cxf/<Iflow Endpoint>/1.1" 500 XXXXms
  
• <IP> - - [<Timestamp>] "GET /cxf/<Iflow Endpoint>/1.1" 500 XXXXms

LJS/Default Trace:

• Servlet.service() for servlet [<some servlet name>] in context with path [<some path>] threw exception [Filter execution threw an exception] with root cause
  

The entries <some servlet name> and <some path> can vary.

In the sender system, you can see only the HTTP 500 error, as an example below (the error depends on which sender system is used):

• 1026:SRT: HTTP-Code 500: ("Internal Server Error")

Note: This error normally occurs after a patch, software update of Cloud Integration, or a restart of the worker node in the Cloud Foundry environment.

• SAP Integration Suite
• SAP Business Technology Platform
• Cloud Integration

Cloud Integration, SAP Integration Suite, SAP Cloud Platform Integration, Cloud Platform Integration, SAP CPI, CPI, SCPI, HANA Cloud Integration, HCI, SAP HCI, tenant, iFlow, Integration Flowm Inbound, Http, 500, Internal, server, error, update, restart, call, fails, fail, failed, failing , KBA , LOD-HCI-PI-CON-SOAP , SOAP Adapter , Problem