SAP Knowledge Base Article - Preview

2940518 - JVM crash randomly after upgrading SAP Mobile Platform

Symptom

After upgrading SAP Mobile Platform to 3.0 SP16 PL10 or SP17 SP01, JVM often crash which caused SMP server to shutdown abnormally.

Checking error.log, you will find JVM crash with SIGSEGV and _S_empty_rep_storage in crash stack as below:

# A fatal error has been detected by the SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=***, pid=***, tid=***
# accessing faulting address: ***
#
# JRE version: Java(TM) SE Runtime Environment (8.0_144) (build 8.1.032)
# Java VM: SAP Java Server VM (8.1.032 25.51-b02 Timestamp - 81_REL - optU - linux amd64 - 6 - bas2:292506 (mixed mode) )
# Problematic frame:
# C [libstdc++.so.6+0x306338] std::string::_Rep::_S_empty_rep_storage+0x18 (sp=***) (pc=***)


Read more...

Environment

  • OS: Linux
  • SAP Mobile Platform 3.0 SP16 PL10 or SP17 PL01

Product

SAP Mobile Platform 3.0 ; SAP Mobile Platform 3.1

Keywords

JVM, crash, CLUSTER, agentry, SMPCommunicationChannel, thread_blocked, abrupt, shutdown, SMP , KBA , MOB-ONP-AGS , SAP Mobile On Premise Agentry Server , 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.