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: 163 of 164 tracked bundles have initialized.
[Too many errors, abort]
/bin/bash: line 1: 16547 Aborted (core dumped) "/SAP/MobilePlatform3/sapjvm_8/bin/java" -server -XtraceFile=log/vm_@PID_trace.log -Dcom.sap.mobile.platform.server.home=/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:/SAP/MobilePlatform3/IntroscopeAgent/wily/Agent.jar" "-Dcom.wily.introscope.agentProfile=/SAP/MobilePlatform3/IntroscopeAgent/wily/core/config/IntroscopeAgent_SMP.profile" "-Dcom.wily.introscope.agent.agentName=MOS_MOS" "-XX:-UseSplitVerifier" -classpath "/SAP/MobilePlatform3/Server/plugins/org.eclipse.equinox.launcher_1.3.0.v20120308-1358.jar":"/SAP/MobilePlatform3/Server/plugins/com.sap.db.jdbc_1.0.49.373159.jar":"/SAP/MobilePlatform3/Server/plugins/org.apache.servicemix.bundles.derby_10.8.2.2_1.jar":"/SAP/MobilePlatform3/Server/plugins/org.apache.commons.codec_1.10.0.jar":"/SAP/MobilePlatform3/Server/plugins/com.springsource.org.apache.commons.lang_2.5.0.jar":/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:

# 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 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-COR , SAP Mobile On Premise Core Services , 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.