2498663 - SMP is not able to start and log file shows SIGSEGV and JVM errors | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2498663 - SMP is not able to start and log file shows SIGSEGV and JVM errors

Symptom

SMP aborts start-up and the log files show the following errors and dump:

SMP server log:

SMPServerStatusManager: 0 of 0 tracked bundles have initialized.
SMPServerStatusManager: 48 of 93 tracked bundles have initialized.
SMPServerStatusManager: 151 of 160 tracked bundles have initialized.
SMPServerStatusManager: 159 of 164 tracked bundles have initialized.
SMPServerStatusManager: 163 of 164 tracked bundles have initialized.
SMPServerStatusManager: 163 of 164 tracked bundles have initialized.
[Too many errors, abort]
/bin/bash: line 1: 16547 Aborted (core dumped) "/sapmnt/MOS/SAP/MobilePlatform3/sapjvm_8/bin/java" -server -XtraceFile=log/vm_@PID_trace.log -Dcom.sap.mobile.platform.server.home=/sapmnt/MOS/SAP/MobilePlatform3/Server "-XX:+HeapDumpOnOutOfMemoryError" "-XX:+DisableExplicitGC" "-Xms4096M" "-Xmx4096M" "-XX:PermSize=256M" "-XX:MaxPermSize=512M" "-XX:ErrorFile=./log/error.log" "-XX:HeapDumpPath=./log/heap_dump.hprof" "-Djava.io.tmpdir=./work/tmp" "-Djava.endorsed.dirs=lib/endorsed" "-Dosgi.logfile=./log/osgi.log" "-DsecretKey=yqvn9bVV4H" "-DsecretKeylength=128" "-Dfile.encoding=UTF-8" "-javaagent:/sapmnt/MOS/SAP/MobilePlatform3/IntroscopeAgent/wily/Agent.jar" "-Dcom.wily.introscope.agentProfile=/sapmnt/MOS/SAP/MobilePlatform3/IntroscopeAgent/wily/core/config/IntroscopeAgent_SMP.profile" "-Dcom.wily.introscope.agent.agentName=MOS_MOS" "-XX:-UseSplitVerifier" -classpath "/sapmnt/MOS/SAP/MobilePlatform3/Server/plugins/org.eclipse.equinox.launcher_1.3.0.v20120308-1358.jar":"/sapmnt/MOS/SAP/MobilePlatform3/Server/plugins/com.sap.db.jdbc_1.0.49.373159.jar":"/sapmnt/MOS/SAP/MobilePlatform3/Server/plugins/org.apache.servicemix.bundles.derby_10.8.2.2_1.jar":"/sapmnt/MOS/SAP/MobilePlatform3/Server/plugins/org.apache.commons.codec_1.10.0.jar":"/sapmnt/MOS/SAP/MobilePlatform3/Server/plugins/com.springsource.org.apache.commons.lang_2.5.0.jar":/sapmnt/MOS/SAP/MobilePlatform3/Server/lib/* org.eclipse.equinox.launcher.Main -console localhost:2401

Server daemon log:

Ping database failed -- Database server not found. //however the DB is up and running

SMP3 SA error log:

Database server stopped at <Date> //however the DB is up and running

The output of go.bat/go.sh:

Using SMP_BASE: /sapmnt/MOS/SAP/MobilePlatform3/Server
Using SMP_HOME: /sapmnt/MOS/SAP/MobilePlatform3/Server
Using JAVA_HOME: /sapmnt/MOS/SAP/MobilePlatform3/sapjvm_8
SQL Anywhere Server Ping Utility Version 17.0.4.2053
Connected to SQL Anywhere 17.0.4.2053 server "smp3" and database "smp3".
Ping database successful.
SMP Server version is 3.0.12.3
Checking DB...
DB connection successful.
Succeeded Version Check.
DB status check to process DML successful.
Checking tcp ports...
TCP ports check successfully.
Prepared war file mobiliser for proper start.
SMPServerStatusManager: SAP Mobile Platform Server is starting. Version: 3.0.12.3 Build: 20161129-1807.
SMPServerStatusManager: 0 of 0 tracked bundles have initialized.
SMPServerStatusManager: 0 of 0 tracked bundles have initialized.
SMPServerStatusManager: 0 of 0 tracked bundles have initialized.
SMPServerStatusManager: 0 of 0 tracked bundles have initialized.
SMPServerStatusManager: 0 of 0 tracked bundles have initialized.
SMPServerStatusManager: 6 of 10 tracked bundles have initialized.
WARNING: Refreshing disabled - Bundle com.sap.mobile.platform.server.online.common.persistence starting - entities may not be woven
WARNING: No persistence descriptors found in persistence bundle com.sap.mobile.platform.server.online.common.persistence
Persistence bundle starting...
Persistence bundle started.
SMPServerStatusManager: 28 of 79 tracked bundles have initialized.
SMPServerStatusManager: 133 of 158 tracked bundles have initialized.
SMPServerStatusManager: 159 of 164 tracked bundles have initialized.
SMPServerStatusManager: 159 of 164 tracked bundles have initialized.
SMPServerStatusManager: 159 of 164 tracked bundles have initialized.
SMPServerStatusManager: 163 of 164 tracked bundles have initialized.
SMPServerStatusManager: 163 of 164 tracked bundles have initialized.
SMPServerStatusManager: 163 of 164 tracked bundles have initialized.
SMPServerStatusManager: 163 of 164 tracked bundles have initialized.
#
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x0000003819f3382f, pid=12242, tid=139892762580736
# accessing faulting address: 0x00007f3b00000000

If SMP can be started, then it fails after sometime and the new log messages are:

SMPServerStatusManager: The SMP server has initialized and is ready.
Gemini Blueprint context shutdown thread ERROR No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Gemini Blueprint context shutdown thread ERROR Unable to register shutdown hook because JVM is shutting down. java.lang.IllegalStateException: Cannot add new shutdown hook as this is not started. Current state: STOPPED


Read more...

Environment

SAP Mobile Platform (SMP) 3.0 OData Runtime

Product

SAP Mobile Platform 3.0

Keywords

sap java virtual machine, jvm, sigsegv, startup, can't start, doesn't start, hangs, hanging , KBA , MOB-ONP , SAP Mobile Platform on Premise , 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.