SAP Mobile Platform 3.0 (SMP3) on Linux crashes in rare circumstances.
And SMP3 server log has no messages, SAP JVM output the error info.
e.g. SAP JVM error message
# # A fatal error has been detected by the SAP Java Virtual Machine: # # SIGSEGV (0xb) at pc=0x00007f49ece407e7, pid=14465, tid=139955211491072 # accessing faulting address: 0x0000000000001008 # # 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 [libmlserv17_r.so+0xea7e7] (sp=0x00007f49dcaa49a8) (pc=0x00007f49ece407e7) # # No core dump will be written (Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again) # # If you would like to submit a bug report, please visit: # https://support.sap.com/incident # Please save the hs_err file(s) and the written core dump for further error analysis # See SAP note 1500116 for further information on collecting core dumps after SAPJVM crashes # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
SAP Mobile Platform 3.0
SMP,down,crash,no response, java, Redhat, segmentation fault , KBA , MOB-ONP , SAP Mobile Platform on Premise , Problem
About this pageThis 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.