SAP Knowledge Base Article - Preview

2498531 - Load balanced HTTPS proxy server for SAP Cloud Connector

Symptom

  • You have completed initial configuration for Cloud Connector and already configured HTTPS Proxy for Cloud Connector to connect to SAP Cloud Platform.
  • However, your proxy server is load balanced which will connect to/between two or more different IP addresses.
  • You encounter with the error situation that on-premise application running on SAP Cloud Platform loses connection to the Cloud Connector every now and then.
  • From Cloud Connector ljs.trc, there is dropout from the Cloud Connector to SAP Cloud Platform can be observed as following for example(establish tunnel to two different IP address):
    -----------------------------------
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.client.notification.NotificationClient#notificationclient-3-2#          #Successfully established tunnel to notification service: [id: 0xcXXXaaab, L:/<Cloud Platform host>:<port> - R:<proxy server host>/<load balanced IP1:<port>]|
    .............
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.core.impl.context.TunnelRegistryImpl#notificationclient-3-2#      #Unregistered tunnel channel [id: 0xcXXXaaab, L:/<Cloud Platform host>:<port> ! R:<proxy server host>/<load balanced IP1:<port>] for tunnel id "account:///<account id>"|
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.core.impl.context.TunnelRegistryImpl#notificationclient-3-2#      #Close tunnel with id "account:///<account id>" and client id "<client id>"|
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.client.reconnect.ReconnectScheduler#notificationclient-3-2#       #Reconnect attempt \#1 to connectivitynotification.ap1.hana.ondemand.com/<client host>:443 - sleeping for 21 seconds|
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.client.handshake.ClientProtocolHandshaker#notificationclient-3-1#  #Sending handshake request for tunnel: account:///<account id> and host connectivitynotification.ap1.hana.ondemand.com|
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.core.impl.context.TunnelRegistryImpl#notificationclient-3-1#          #Registered tunnel channel [id: 0x8XXXe3cd, L:/<Cloud Platform host>:<port> - R:<proxy server host>/<load balanced IP2:<port>] for tunnel id "account:///cf6e9a8d5" and client id"69294A805F8D11E6B7EFD4650AA029C5"|
    <Timestamp>#INFO#com.sap.core.connectivity.tunnel.client.notification.NotificationClient#notificationclient-3-1#          #Successfully established tunnel to notification service: [id: 0x8XXXe3cd, L:/<Cloud Platform host>:<port> - R:<proxy server host>/<load balanced IP2:<port>]|
    -----------------------------------

Read more...

Environment

  • SAP Cloud Connector
  • SAP Cloud Platform

Product

SAP Cloud Platform Connectivity 2.0 ; SAP Cloud Platform all versions ; cloud connector 1.0 for SAP HANA Cloud Platform

Keywords

Cloud Connector, SAP Cloud Platform, SCC, SCP, HTTPS proxy, proxy server, tunnel, connection dropout, connection reconnect, load balanced proxy server , 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 ONE Support launchpad (Login required).

Search for additional results

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