Symptom
- When trying to start the instance, it crashes in the startup phase.
- In the hs_err_pid<pid>.log the JVM crash info will be written with an entry in the logs similar to:
#
# An unexpected error has been detected by SAP Java Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xffffffff77cf5df8, pid=508, tid=1220
#
# Java VM: SAP Java 64-Bit Server VM (5.1.020 Apr 18 2008 04:15:33 - 01_REL - optU - solaris sparc - bas2:98593 (mixed mode))
# Problematic frame:
# V libjvm::int VMCMutex::lock()+0xe8 (0x1cf5df8) (sp=0xfffffffde50ff690) (pc=0xffffffff77cf5df8)
#
Read more...
Environment
- SAP NetWeaver Application Server Java
- Solaris Operating System
Product
Keywords
SAP, JVM, SAPJVM, Solaris, crash, Crashinfo, SIGSEGV, SAP Java Virtual Machine, Java, Virtual Machine, VM, sparc, startup, EnableDebuggingOnDemand, upgrade, debug, netweaver, as, application server, application, server, issue, configtool, config, tool, parameters, additional , KBA , BC-JVM , SAP Java Virtual Machine , 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.