Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionPrageetika Sharma
2017-07-19 16:18:25 UTC
Description of problem:
The shutdown wait option for Tomcat is not working for RHEL7 servers.
Version-Release number of selected component (if applicable):
tomcat-7.0.69-11.el7_3.noarch
How reproducible:
Steps to Reproduce:
1. Install the tomcat
2. Set SHUTDOWN_WAIT in /usr/share/tomcat/conf/tomcat.conf
##########################################
# Time to wait in seconds, before killing process
# TODO(stingray): does nothing, fix.
SHUTDOWN_WAIT="30"
SHUTDOWN_VERBOSE="true"
##########################################
3. Restart Tomcat
Actual results:
Tomcat shutdown immediately.
Expected results:
Tomcat should wait for 30 sec before shutting down.
Additional info:
> # Time to wait in seconds, before killing process
The comment in the conf file is wrong...
First, SHUTDOWN_WAIT is the amount of time that the tomcat script waits AFTER it submits a shutdown before it kills the process. Second, this doesn't apply to systemd's service unit and that comment/variable should be removed from the configuration. You can use https://www.freedesktop.org/software/systemd/man/systemd.service.html#TimeoutStopSec= instead, which defaults to 90s instead of tomcat's previous SHUTDOWN_WAIT of 30s.
I updated the comment in tomcat.conf and tomcat's sysconfig files to state that SHUTDOWN_WAIT is deprecated and suggest that users use TimeoutStopSec instead. I didn't add TimeoutStopSec to the systemd service unit because it's been this way for quite a long time and nobody has complained until now, so users can add (and probably already have added) it on their own.
Additionally, I took the opportunity to cleanup the sysconfig file a bit more and remove the following deprecated variables (in addition to SHUTDOWN_WAIT): TOMCAT_USER, SHUTDOWN_VERBOSE, and CONNECTOR_PORT. These variables were leftover from the sysV script and should have been removed when we switched over to systemd.
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-2019:2205