2483316 - SAP JVM crash: SAP Cloud Connector fails to start

The SAP Cloud Platform Cloud Connector does not start due to the SAP Java Virtual Machine crashing and errors similar to the below are recorded in the traces:

*******************************************************************
# A fatal error has been detected by the SAP Java Virtual Machine:
#  SIGSEGV (0xb) at pc=0x00007f79164d6115, pid=17671, tid=140157542340352
# accessing faulting address: 0x0000000000000004
# JRE version: Java(TM) SE Runtime Environment
# Java VM: SAP Java Server VM
# Problematic frame:
# C  [libc.so.6+0xa7115]  readdir_r+0x45 (sp=0x00007f78f885fda0) (pc=0x00007f79164d6115)
# No core dump will be written (Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again)
# An error report file with more information is saved as:
# /opt/sap/scc/hs_err_pid17671.log
[thread 140157538137856 also had an error (0xb)
Details: pc=0x00007f7903dfd6d0 siginfo: si_signo: 11 (SIGSEGV), si_code: 2 (SEGV_ACCERR), si_addr: 0x00007f7916ddc080]

# If you would like to submit a bug report, please visit:
# Please save the hs_err file(s) and the written core dump for further error analysis
# See SAP note 1500116 for further information on collecting core dumps after SAPJVM crashes
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

*******************************************************************

• SAP Cloud Platform Cloud Connector
• Release Independent

Production ABAP R/3 ERP SRM CRM ERP PPM SEM APO XI PI PORTAL Test development QA SSLEngine, problem, Cloud, Connector SIGSEGV accessing faulting address JRE version Java(TM) SE Runtime Environment Problematic frame SAP note 1500116 SAP Cloud Platform Cloud Connector directory /opt/sap/scc /sap/scc native layer de-reference null-pointer SAP JVM 7 SAP JVM 8 SAP Note 1442124 SAP Note 1367498 , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , Problem