SAP Knowledge Base Article - Preview

3624179 - Messaging to an on-premise backend system fails with statusCode: 503

Symptom

You use SAP Cloud Platform Integration(CPI) to help transfer messages to an on-premise system via SAP Cloud Connector. 
You notice the message processing fails with the following error shown in CPI monitoring UI:
>>>
Error Details
com.sap.it.rt.adapter.http.api.exception.HttpResponseException: An internal server error occured: HTTP operation failed invoking http://<detination host>:<port>/<service> with statusCode: 503. The MPL ID for the failed message is : *****
<<<
 
By enabling the log level of the target iFlow to INFO, you will see the corresponding outbound call has a response body like the following:
>>>
There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount <ID>; and SCC location ID, with default value, that is empty string or simply not configured. Check the configuration on SCC and cloud side. 
<<<


Read more...

Environment

  • SAP Cloud Platform Integration
  • SAP Cloud Connector release independent

Product

Cloud Integration all versions ; SAP Connectivity service all versions

Keywords

connectivitynotification; connection timed out; 503; internal server error; cloud connector; SCC; Cloud Integration; , KBA , LOD-HCI-PI-CON-HTP , HTTP Adapter , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.