RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1229476 - Tomcat startup ONLY options
Summary: Tomcat startup ONLY options
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tomcat
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Coty Sutherland
QA Contact: fgoldefu
URL:
Whiteboard:
Depends On:
Blocks: 1203710 1298191 1313485
TreeView+ depends on / blocked
 
Reported: 2015-06-08 21:31 UTC by David Knox
Modified: 2019-07-11 09:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 21:08:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Fix proivded by David which closed the case, but didn't go into the bug it seems (758 bytes, patch)
2015-11-10 12:46 UTC, Coty Sutherland
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2599 0 normal SHIPPED_LIVE Moderate: tomcat security, bug fix, and enhancement update 2016-11-03 12:12:12 UTC

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


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