Symptom
Multiple entries can be seen in the SAP Cloud Connector (SCC) logs (ljs_trace.log (<2.17)/scc_core.trc (>=2.17), like the following:
"<YYYY/MM/DD> <Timestamp> #DEBUG#com.sap.core.connectivity.spi.processing.OutboundConnectionErrorHandler#tunnel-client-64-1#<ID>#Backend channel [id: <ConnectionID>, L:/<LocalHost> ! R:<RemoteHost>/<IP_Address>] is closed
<YYYY/MM/DD> <Timestamp> #ERROR#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-64-2#<ID>#Discarding packet as connection to backend has been unexpectedly closed"
**Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
SAP Cloud Connector release independent.
Product
Keywords
SCC, SAP Cloud Connector, #Discarding packet as connection to backend has been unexpectedly closed, ftp server, backend, network, firewall, backend channel is closed, ljs_trace.log, java.io.EOFException: Connection closed by remote host, network connectivity, backend released, scc_core.trc, cc, tunnel-client, , KBA , 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.
SAP Knowledge Base Article - Preview