Bug 1387439 - Missing Tomcat's default setting for the max heap size.
Summary: Missing Tomcat's default setting for the max heap size.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 21:33 UTC by Prashant Waghmare
Modified: 2019-12-16 07:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-11 17:24:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Prashant Waghmare 2016-10-20 21:33:54 UTC 
Description of problem:

On freshly installed satellite 6.2.2 customer is getting out of memory error for tomcat. He corrected the parameters by manually editing the conf file for tomcat. which suggest a reasonable default setting for the max heap size was missing."

Version-Release number of selected component (if applicable):

satellite6.2.2

How reproducible:

Always.

Steps to Reproduce:

1. Install fresh satellite 6.2.2

2.vi /etc/sysconfig/tomcat

JAVA_OPTS="-Xminf0.1 -Xmaxf0.3"

3. .

Actual results:

Due to this less value, getting out-of memory error for tomcat

Expected results:

The default value of JAVA_OPTS should be sufficient enough so that it could not go out-of memory for tomcat.

Additional info:
Comment 2 Chris Roberts 2016-11-11 17:24:15 UTC 
With Candlepin 2.0 coming up and needing more memory and talking to the Candlepin folks since this is a 1 off case, and no other customers have hit this I am closing this out. If you feel this should be reopened feel free to reopen the BZ.

- Chris Roberts
Note You need to log in before you can comment on or make changes to this bug.