...
Code Block | ||
---|---|---|
| ||
# # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (malloc) failed to allocate 32744 bytes for ChunkPool::allocate # Possible reasons: # The system is out of physical RAM or swap space # In 32 bit mode, the process size limit was hit # Possible solutions: # Reduce memory load on the system # Increase physical memory or swap space # Check if swap backing store is full # Use 64 bit Java on a 64 bit OS # Decrease Java heap size (-Xmx/-Xms) # Decrease number of Java threads # Decrease Java thread stack sizes (-Xss) # Set larger code cache with -XX:ReservedCodeCacheSize= # This output file may be truncated or incomplete. # # Out of Memory Error (allocation.cpp:273), pid=5092, tid=6740 # # JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode windows-amd64 compressed oops) # Core dump written. Default location: C:\ProgramData\sos-berlin.com\jobscheduler\extsrvsdl01vprd_4444\hs_err_pid5092.mdmp # |
Increment/Decrement for only one job using Java
...
- Please consider the different strategies of Java heap space usage covered in the article How to manage the Java heap space
- For possible JVM options please see the Java documention
...