Symptom
There is a case that SIGSEGV occurred during stopping SAP Mobile Platform 3.0 (SMP3) on Linux.
It logged on osgi.log
e.g.
#
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x00007f15ef58af43, pid=23898, tid=139732226807552
# accessing faulting address: 0x00007f15ef58af43
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45) (build 8.1.008)
# Java VM: SAP Java Server VM (8.1.008 25.45-b02 Jun 17 2015 18:11:29 - 81_REL - optU - linux amd64 - 6 - bas2:242406 (mixed mode) compressed oops)
# Problematic frame:
# C 0x00007f15ef58af43 (sp=0x00007f15f1be0eb8) (pc=0x00007f15ef58af43)
#
# No core dump will be written (Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again)
#
There is possibility that the error causes SMP3 server boot trouble by osgi cache problem.
Please see "See Also" for the SMP3 boot trouble.
Read more...
Environment
SAP Mobile Platform 3.0 SP11, SP12 on Linux
Product
Keywords
SMP3, SIGSEGV, segmentation fault, Linux, osgi error , 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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.