Article - CS268413
ThingWorx Server Crashes With Error "Out of memory: Kill process <Process ID> (java) score <score> or sacrifice child"
Modified: 04-Mar-2026
Applies To
- ThingWorx Platform 7.4 to 9.6
Description
- ThingWorx server failing to start
- Error in /var/log/messages.log
Out of memory: Kill process <Process ID> (java) score <score> or sacrifice child
kernel: java invoked oom-killer- Apache Tomcat process is stopped
- High CPU Usage and Access Issues on ThingWorx Application Server
- URL is not coming up after restarting
- Application stopped with status OOMKilled
- hs_err_pid.log reports
# There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (malloc) failed to allocate 2064 bytes for AllocateHeap # 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 # Possible solutions: # Reduce memory load on the system # Increase physical memory or swap space # Check if swap backing store is full # Decrease Java heap size (-Xmx/-Xms) # Decrease number of Java threads # Decrease Java thread stack sizes (-Xss) # Set larger code cache with -XX:ReservedCodeCacheSize= # JVM is running with Zero Based Compressed Oops mode in which the Java heap is # placed in the first 32GB address space. The Java Heap base address is the # maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress # to set the Java Heap base and to place the Java Heap above 32GB virtual address.
- Frequent stability and performance issues observed on the ThingWorx server shutting down multiple times per day, causing operational disruption
This is a printer-friendly version of Article 268413 and may be out of date. For the latest version click CS268413