This question was originally posted on DCIM Support by John Smith on 2018-05-08
I am getting this error in hs_err_pid680.log. Any thoughts?
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (nmap) failed to allocate 310378496 bytes for committing reserved memory.
# 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 (os_linux.cpp:2627), pid=680, tid=0x00007f126d07e700
# JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode Linux-amd64 compressed oops)
This comment was originally posted on DCIM Support by spezialist on 2018-05-08
Dear John Smith,
Under what circumstances did the above problem occur?
Did this issue occur while the Linux desktop DCE-client was running?
This comment was originally posted on DCIM Support by John Smith on 2018-05-09
That issue was found in the DCE Server logs. Not the client. I only have windows clients installed.
This answer was originally posted on DCIM Support by spezialist on 2018-05-10
Dear John Smith,
Unfortunately, it's not easy to tell the root cause of the above JVM error on the DCE-server ☹️. You can, of course, point out the lack of RAM, but this is only true if your DCE-server has only 1GB of RAM (i.e., Basic DCE appliance), and the number of monitoring devices reaches up to a thousand.
Therefore, if this problem is not frequent and regular and does not involve a real lack of RAM, then I recommend simply updating your DCE-server to the latest version 7.5.0. This is a good practice, because judging by your log-file, the JVM version is old (latest version is 1.8.0_171), and updating the DCE-server you get also the latest version of JVM, which is very important for the normal operation of DCE software.
This comment was originally posted on DCIM Support by John Smith on 2018-05-10
Thanks. The server has plenty of RAM, I think it is 16 or 20GB and 5 Cores. It should be flying!
Discuss challenges and get support in energy and automation with 30,000+ experts and peers.
Over 10,000+ support articles are available to help you find answers to your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!