Tomcat Is Crashing Frequently With Error 'Cannot allocate memory' In Catalina.out and hs_err_pid*.log Getting Generated.
(Doc ID 2906868.1)
Last updated on APRIL 28, 2023
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
AI tomcat was crashing very frequently.
Errors observed in Catalina.out:
CMGR WARNING] Removing connection pool siebel.TCPIP.NONE.NONE://[Hostname]:[Port]/[Enterprise_Name]/eSalesObjMgr_sve/!1.7daf3
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000793980000, 463470592, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 463470592 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /opt/siebel/sweapp/esales/sweapp/applicationcontainer_external/bin/hs_err_pid748876.log
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000793980000, 463470592, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 463470592 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /opt/siebel/sweapp/esales/sweapp/applicationcontainer_external/bin/hs_err_pid748876.log
In hs_err_pid748876.log we could see:
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 12288 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Native memory allocation (mmap) failed to map 12288 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
Changes
No major change done to the environment.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |