Description of problem:
By default, Satellite will not set -Xmx in tomcat.conf. This can lead to situations where the JVM for candlepin will consume large amounts of memory, for example when performing large numbers of system registrations. Eventually, the OOM killer will kick in and likely kill the java process.
Version-Release number of selected component (if applicable): 6.2.6
How reproducible: every time
Steps to Reproduce:
1. peform a large number of system registrations (perhaps over 10,000 in one go)
2. observe java memory footprint
Actual results: java will grow up to 1/4 the size of memory
Expected results: the heap will stop at some predetermined amount, allowing for memory for other processes. Ideally, we could set at 6GB by default but make it configurable via an installer option.
Additional info: This is likely not a candlepin memory issue. The JVM thinks it has all that memory available, and is going to use it. Setting the Xmx flag leaves space for other processes.
This didn't cherry-pick cleanly, and I'm not that familiar with the codebase. Could you do the pick for me?
Not a problem, I will do it tomorrow after my RHEV Exam.
On satellite 6.3 snap 29:
# grep Xmx /etc/tomcat/tomcat.conf
Thus I am moving this BZ to VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > For information on the advisory, and where to find the updated files, follow the link below.
> > If the solution does not work for you, open a new bug report.
> > https://access.redhat.com/errata/RHSA-2018:0336