SAP Knowledge Base Article - Preview

3654365 - error 32 broken pipe while setting up Cloud ALM with SAP Cloud Connector

Symptom

While setting Cloud ALM with SCC for monitoring purposes, you come across to following error while performing a connection test from the SCC mapping, same can be perceived from SCC trace (ljs_trace.log / scc_core.trc) after a connection test is triggered from SCC.


===
Message:
Network Issue

Exception:
java.net.SocketException: error 32 - Broken pipe (Write failed) (local port XXXXX to address XX.XX.XX.XX), remote host unknown)
===


Read more...

Environment

  • SAP Cloud Connector(SCC) release independent;
  • SAP Cloud ALM.

Keywords

java.net.SocketException, error 32, Broken pipe, Write failed, remote host unknown, SAP Cloud connector, cloud connector, connector, SAP CC, SAP SCC, SCC, timeout, time out, timed out, local host, localhost, cloud alm, ALM, cloud monitoring,  , KBA , SV-CLM , SAP Cloud ALM , 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.