3320953 - Switch over fails with error "Data transfer to shadow failed" in a high availability configuration

Symptom

A switch over from master to shadow cloud connector triggers the highlighted alert :-

Issues with the sync of subaccount certificates to the shadow can also be notice after the certificate renewal in master or after a switch over.

Ljs_trace.log from master reports error :-

Push transfer failed caused by com.sap.scc.ha.HaHttpClientException: request https://<hostname>:8443/shadow failed with 500 () <!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1></body></html> with alert Data transfer to shadow system failed. See ''Log And Trace Files'' and in particular ljs_trace.log for details.
com.sap.scc.ha.PushRequestException: com.sap.scc.ha.HaHttpClientException: request https://<hostname:port>/shadow failed with 500 () <!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1></body></html>
at com.sap.scc.ha.PushRequest.failed(PushRequest.java:107)
at com.sap.scc.ha.PushRequest.execute(PushRequest.java:70)
at com.sap.scc.ha.PushRequestChain.execute(PushRequestChain.java:18)
at com.sap.scc.ha.PushToShadow.lambda$new$0(PushToShadow.java:76)
at com.sap.scc.ha.PushRequest.execute(PushRequest.java:78)
at com.sap.scc.ha.PushExecutor.run(PushExecutor.java:52)
at java.lang.Thread.run(Thread.java:838)

Ljs_trace.log from shadow reports error :-

2023-02-28 09:02:41,001 -0800#TRACE#com.sap.scc.ui#https-jsse-nio2-8443-exec-2# #execute incoming request /shadow with action 'updateConfig'
2023-02-28 09:02:41,001 -0800#DEBUG#com.sap.scc.ui#https-jsse-nio2-8443-exec-2# #Shadow <host>: Master pushes update configuration for <subaccount ID> update type = update
2023-02-28 09:02:41,048 -0800#TRACE#com.sap.scc.ui#https-jsse-nio2-8443-exec-2# #incoming request /shadow action: updateConfig finished after 47 ms
2023-02-28 09:02:41,048 -0800#TRACE#com.sap.scc.ui#https-jsse-nio2-8443-exec-6# #execute incoming request /shadow with action 'updateKeyStore'
2023-02-28 09:02:41,048 -0800#DEBUG#com.sap.scc.ui#https-jsse-nio2-8443-exec-6# #Shadow <host>: Master pushes update keystore for <subaccount ID>
2023-02-28 09:02:41,048 -0800#ERROR#com.sap.scc.ui#https-jsse-nio2-8443-exec-6# #Unhandled runtime exception
java.lang.NullPointerException: while trying to invoke the method com.sap.scc.info.SupportInfo.getSccVersion() of a null object returned from com.sap.scc.ha.PingToMaster.getMasterSupportInfo()

Environment

SAP Cloud Connector 2.15.1

Keywords

SAP Cloud Connector, SCC, Switch Roles, Switch Over, Failover, High Availability, 2,15.1, Master, Shadow, HTTP Status 500 – Internal Server Error, Data transfer to shadow failed, , 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.