/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
SAP Cloud Connector can not connect to notification server, and following exception is perceived from SCC trace (ljs_trace.log):
Unable to handshake with notification server connectivitynotification.<region>.hana.ondemand.com/<IP address> java.nio.channels.ClosedChannelException [...]q Tunnel handshake failed! Closing the tunnel channel immediately java.nio.channels.ClosedChannelException [...] Could not open tunnel account:///<subaccount> to cloud. com.sap.scc.servlets.RequestFailureExecution$IllegalState: RequestFailureExecution |
Read more...
Environment
- SAP Cloud Connector release independent;
- SAP BTP cloud environment.
Product
SAP Connectivity service 2.0
Keywords
SAP Cloud Connector, SCC, connectivity, Unable to handshake with notification server, Tunnel handshake failed, RequestFailureExecution, BTP, cockpit, SAP CC, SAPCC, Connector, handshake, connectivitynotification , KBA , scp , cloud platform , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)