SAP Knowledge Base Article - Preview

2650368 - SAP Cloud Connector High Availability scenario does not work - HTTPException - 502: Bad Gateway'

Symptom

SAP Cloud Connector High Availibality scenarion does not work properly. With the Master instance the iflow is working fine from HCI to backend system via SAP Cloud Connector, but when the Shadow instance becomes the Master role, the HCI message flow fails with the following exception in ljs_trace:

[...]
#ERROR#org.apache.camel.processor.FatalFallbackErrorHandler##anonymous#default-workqueue-1#na#avphcie#e0967iflmap#web##na#na#na#na#\\--> New exception on exchangeId: ID-vsa3637543-60033-1523659278049-5-251org.apache.cxf.interceptor.Fault: Could not send Message.
[...]
Caused by: org.apache.cxf.transport.http.HTTPException: HTTP response '502: Bad Gateway' when communicating with <XXXXXX>
[...]


Read more...

Environment

SAP Cloud Connector with High Availability scenario

Product

SAP Cloud Platform Connectivity 2.0

Keywords

SAP Cloud Connector, High Availability, HTTPException, 502: Bad Gateway, 502 Bad Gateway, '502: Bad Gateway', FatalFallbackErrorHandler , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-NEO-CON , 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 ONE Support launchpad (Login required).

Search for additional results

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