Symptom
SAP Cloud Connector (SCC) fails to connect to a backend system with the following error, which can be found in SCC trace (ljs_trace.log / scc_core.trc), and may be propagated to an application running on SAP Cloud Platform:
| #ERROR#com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler#processor-7-11#0xb17c96bb#Internalerror java.io.IOException: An existing connection was forcibly closed by the remote host at sun.nio.ch.SocketDispatcher.read0(Native Method) |
Read more...
Environment
SAP Cloud Connector release independent
Product
Keywords
Destination, OData, Gateway, Cloud Connector, CONN, closed, 307, no_response, http, RFC, SCC, Internal host, virtual host, communication, back-end, backend, conn, connection closed, outbound connection, errorhandler, internal error, internalerror, forcibly, closed by remote, nio.ch, socketdispatcher, java.io.IOException,forcibly closed, sun.nio.ch , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-NEO-CON , Neo to On-premise Connectivity service , 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.
SAP Knowledge Base Article - Preview