SAP Knowledge Base Article - Preview

3699210 - Unable to access SAP Cloud Connector after upgrade.

Symptom

  • Unable to open the SAP Cloud Connector URL after upgrade.
  • Blank page displayed after entering user credentials in the SAP Cloud Connector URL.
  • Port 8443 is not listening on the server despite the daemon service being started.
  • Error messages observed in the scc_service or the daemon_scc(for Linux) logs:
    #ERROR#org.apache.catalina.startup.Catalina#CloudConnectorMainThread#          #The required Server component failed to start so Tomcat is unable to start.
    org.apache.catalina.LifecycleException: Failed to start component [StandardServer[-1]]
            at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:406)
            at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:179)
            at org.apache.catalina.startup.Catalina.start(Catalina.java:739)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
            at java.lang.reflect.Method.invoke(Method.java:498)
            at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
            at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)
            at com.sap.scc.tomcat.utils.SCCBootStrap.lambda$main$0(SCCBootStrap.java:32)
            at java.lang.Thread.run(Thread.java:750)
    Caused by: java.lang.NoClassDefFoundError: com/sun/tools/attach/AttachNotSupportedException
            at com.sap.core.js.monitoring.MBeansFactory.<init>(MBeansFactory.java:50)
            at com.sap.core.js.monitoring.MonitoringLifecycleHandler.<init>(MonitoringLifecycleHandler.java:18)
            at com.sap.core.js.monitoring.MonitoringLifecycle.start(MonitoringLifecycle.java:16)
            at com.sap.cloud.runtime.kotyo.lifecycle.InternalComponentLifecycleManager.startInternalComponents(InternalComponentLifecycleManager.java:41)
            at com.sap.cloud.runtime.kotyo.lifecycle.InternalComponentLifecycleManager.lifecycleEvent(InternalComponentLifecycleManager.java:31)
            at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:109)
            at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:389)
            at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:336)
            at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:862)
            at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)
            ... 9 common frames omitted
    Caused by: java.lang.ClassNotFoundException: com.sun.tools.attach.AttachNotSupportedException
            at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
            at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
            ... 19 common frames omitted 
  • Or error in the scc_service or the daemon_scc logs:

    #ERROR#org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/].[jsp]#https-jsse-nio2-8443-exec-5#          #Servlet.service() for servlet [jsp] in context with path [] threw exception [An exception occurred processing [js/log_view.js] at line [192]
    189:                                    tooltip: '<%= Tools.getTextForJS(locale, "tooltip.printStackDump") %>',
    190:                                    hideText: false,
    191:                                    press: () => {
    192:                                            UIFactory.showConfirmDialog('<%= Tools.getTextForJS(locale, (JvmUtils.get().isSapJvm()) ? "message.confirm.printStackDump" : "message.confirm.printStackDumpOnNonSapJvm") %>',
    193:                                                    confirmed => {
    194:                                                            if (confirmed)
    195:                                                            {

    Stacktrace:] with root cause
    java.lang.NullPointerException: null
            at com.sap.jvm.APIFactory.getMaxThreadAnnotations(APIFactory.java:370)
            at com.sap.jvm.monitor.vm.ThreadAnnotationKey.<clinit>(ThreadAnnotationKey.java:228)
            at java.lang.Class.forName0(Native Method)
            at java.lang.Class.forName(Class.java:264)...

**Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

SAP Cloud Connector release independent.

Product

CONNECTOR FRAMEWORK all versions ; SAP Connectivity service all versions

Keywords

sap cloud connector, upgrade, version 2.16 to 2.18, port 8443 not listening, tomcat failed to start, java.lang.NoClassDefFoundError, java.lang.NullPointerException, java.lang.ClassNotFoundException, blank page, sap jvm, tools.jar, jdk, daemon service, cloud connector URL, runtime error, incomplete installation, corrupted sap jvm, systemd configuration , 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.