Symptom
The SAP Application Server Java startup fails due to SAP JVM (Java Virtual Machine) crashing and the below error is logged in the JVM trace file (hs_err_pid.log):
*********************************************************
# A fatal error has been detected by the SAP Java Virtual Machine:
#
# Internal Error (interpreter/interpreter.hpp:112), pid=<<pid>>, tid=<<tid>>
# guarantee(codelet_size > 0 && (size_t)codelet_size > 2*K) failed: not enough space for interpreter generation
*********************************************************
Read more...
Environment
- SAP NetWeaver Application Server Java
- Release Independent
Product
Keywords
(mixed mode) compressed oops, DEBUG, !ASSERT, PRODUCT, java.lang.NoSuchMethodError, java.util.concurrent.ThreadPoolExecutor.allowCoreThreadTimeOut(Z)V, exit code 67, com.sap.sql.connect.pool.Pool.start, SAP JAVA versions, SAPJVM versions, Deployment of queue 1367498 1133020 2167686 1916755 1442124 ,SAP Production ERP SRM CRM ERP PPM SEM APO XI PI PORTAL issue , KBA , BC-JVM , SAP Java Virtual Machine , BC-JAS-SF , Startup Framework , 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.