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.

Description of problem:

Inside /usr/libexec/tomcat/preamble the following is found. 

CLASSPATH="${CLASSPATH}${CATALINA_HOME}/bin/bootstrap.jar"
CLASSPATH="${CLASSPATH}:${CATALINA_HOME}/bin/tomcat-juli.jar"
CLASSPATH="${CLASSPATH}:$(build-classpath commons-daemon 2>/dev/null)"

by coding the tomcat-juli.jar to CATALINA_HOME instead of CATALINA_BASE which will default to CATALINA_HOME if not defined then you prevent the usage of using other types of logging specifically log4j for tomcat, when multiple catalina_base's are set. 

From the documentation of tomcat: 
If you are running Tomcat with separate $CATALINA_HOME and $CATALINA_BASE and want to configure to use log4j in a single $CATALINA_BASE only:

Create $CATALINA_BASE/bin and $CATALINA_BASE/lib directories if they do not exist.
Put log4j.jar and tomcat-juli-adapters.jar from "extras" into $CATALINA_BASE/lib
Put tomcat-juli.jar from "extras" as $CATALINA_BASE/bin/tomcat-juli.jar 

https://tomcat.apache.org/tomcat-8.0-doc/logging.html
https://tomcat.apache.org/tomcat-7.0-doc/logging.html

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


How reproducible:


Steps to Reproduce:
1. Install tomcat
2. set a base in /var/lib/tomcats/
3. create unit file for new base 
4) start tomcat and view output

Actual results:



Expected results:


Additional info:

There is no epel7 package for tomcat, so are you referring to the RHEL 7 package, or the Fedora one?

RHEL, apologies.

No problem, I'll move it to the correct product so we can get it sorted out for you.

To resolve this issue, the classpath setting in the preamble:

    CLASSPATH="${CLASSPATH}:${CATALINA_HOME}/bin/tomcat-juli.jar"

should be updated to use CATALINA_BASE:

    CLASSPATH="${CLASSPATH}:${CATALINA_BASE}/bin/tomcat-juli.jar"

This change will continue to work as normal (defaulting CATALINA_BASE back to CATALINA_HOME), unless you're using the named service in which case it will pick up tomcat-juli.jar from the ${CATALINA_BASE}/bin/ instead of ${CATALINA_HOME}/bin/.

Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.