Bug 1229476

Summary: Tomcat startup ONLY options
Product: Red Hat Enterprise Linux 7 Reporter: David Knox <dknox>
Component: tomcatAssignee: Coty Sutherland <csutherl>
Status: CLOSED ERRATA QA Contact: fgoldefu
Severity: low Docs Contact:
Priority: medium    
Version: 7.0CC: csutherl, jclere, mbabacek, rhatlapa
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 21:08:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1203710, 1298191, 1313485    
Attachments:
Description Flags
Fix proivded by David which closed the case, but didn't go into the bug it seems none

Description David Knox 2015-06-08 21:31:17 UTC 
Description of problem:
In this case, the customer would like to use options that
apply only at startup. The OS is RHEL 7 and the package in use is 7.0.54. They were using CATALINA_OPTS previously and it worked fine, but with the rebase we re-implemented all of the systemd service scripts and apparently this functionality was removed/forgotten.

the scripts used by systemd are completely different from the ones used previously on rhel-7/tomcat7. the ExecStart/Stop call different scripts

Version-Release number of selected component (if applicable):
tomcat7 for rhel-7.0, 7.1, 7.2, & potentially 7.3

How reproducible:
Always -- Add a Java system property and start tomcat. tomcat will use CATALINA_OPTS and JAVA_OPTS both at start and stop. stopping tomcat could lead to errors e.g., if a port (like a jmx port), is opened. 

Actual results:
An error when stopping tomcat 

Expected results:
no error


Additional info:
Comment 4 Coty Sutherland 2015-11-10 12:46:13 UTC 
Created attachment 1092226 [details]
Fix proivded by David which closed the case, but didn't go into the bug it seems
Comment 13 errata-xmlrpc 2016-11-03 21:08:59 UTC 
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://rhn.redhat.com/errata/RHSA-2016-2599.html