Reporting within the console hanging or failing
Not enough memory, increase memory in the jvmargs.cfg file.
The memory settings information can be found at <install_dir>/jvmargs.cfg as per below:
###############################################################################
####################### JVM memory tuning suggestions ########################
###############################################################################
# #
# Select the initial or start, and maximum memory sizes available to the JVM; #
# (-Xms, -Xmx) respectively. #
# These values are used for the JVM heap, which reserves memory for the #
# server and its database (DB). #
# Increasing the amount of memory available can improve performance, but #
# increasing it to too high a value can have a detrimental effect in the form #
# of longer pauses for full garbage collection runs. Setting -Xms and -Xmx to #
# the same value increases predictability by removing the most important #
# sizing decision from the virtual machine. On the other hand, the virtual #
# machine can't compensate if you make a poor choice. Be sure to increase the #
# memory as you increase the number of processors, since allocation can be #
# parallelized. JVM heaps greater than 4 Gbytes require a 64-bit JVM. #
# #
# Numbers can include 'm' or 'M' for megabytes, 'k' or 'K' for kilobytes, and #
# 'g' or 'G' for gigabytes (for example, 32k is the same as 32768) #
# #
# Unless you have problems with pauses, try granting as much memory as #
# possible. #
# #
###############################################################################
# #
# For further reading on garbage collection tuning refer to #
# <http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html> #
# and for additional VM options refer to #
# <http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp> #
# #
###############################################################################
# #
###############################################################################
################# Recommended JVM memory and tuning settings #################
###############################################################################
# The specifications outlined below depend on reporting demands. #
# If reporting demand is heavy (more than 2-3 reports being generate #
# simultaneously), you will need to increase the memory from the suggested #
# values outlined below. #
# #
# 20m per 1000 records (hosts,users,groups,group memberships) should support #
# 1-3 simultaneous clients. #
# 30m per 1000 records (hosts,users,groups,group memberships) should support #
# 3-5 simultaneous clients. #
# #
# Example settings: #
# -Xms512m #
# -Xmx512m #
###############################################################################
# #
-Xms512m
-Xmx512m
-XX:MaxPermSize=128M
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center