Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Won't Do
Priority: Major
Fix Version/s: None
Affects Version/s: JWS 3.1.0 GA
Component/s: rpm, tomcat
Labels:
- jws-pool
- moved-from-jws500-to-jws500sp1

Story Points:
1
Affects:

Release Notes
Target Release:

5.2.0.GA
Workaround:

Workaround Exists
Workaround Description:
Hide

Disable the ConsoleAppender. Note that some messages will still be printed, like flags used, etc. Those are actual output of the startup script and are around 10 lines total.

--- /etc/tomcat8/logging.properties.orig 2017-06-30 10:37:50.171000000 -0400 +++ /etc/tomcat8/logging.properties 2017-06-30 10:38:07.499000000 -0400 @@ -13,9 +13,9 @@ # See the License for the specific language governing permissions and # limitations under the License. -handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler +handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler -.handlers = 1catalina.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler +.handlers = 1catalina.org.apache.juli.AsyncFileHandler ############################################################ # Handler specific properties.
Show
Disable the ConsoleAppender. Note that some messages will still be printed, like flags used, etc. Those are actual output of the startup script and are around 10 lines total. --- /etc/tomcat8/logging.properties.orig 2017-06-30 10:37:50.171000000 -0400 +++ /etc/tomcat8/logging.properties 2017-06-30 10:38:07.499000000 -0400 @@ -13,9 +13,9 @@ # See the License for the specific language governing permissions and # limitations under the License. -handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler +handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler -.handlers = 1catalina.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler +.handlers = 1catalina.org.apache.juli.AsyncFileHandler ############################################################ # Handler specific properties.
Steps to Reproduce:

Hide

1) Install tomcat RPM
2) Start tomcat
3) Observe missing catalina.out and the whole tomcat log being written to /var/log/messages

Show
1) Install tomcat RPM 2) Start tomcat 3) Observe missing catalina.out and the whole tomcat log being written to /var/log/messages

SFDC Cases Links:
SFDC Cases Counter:

Description

After moving Tomcat to systemd service units I neglected to disable the ConsoleAppender that was previously creating the catalina.out file. Now tomcat creates a catalina.log in it's log directory and directs all other output (everything by default) to the journal (and therefore /var/log/messages on rhel-7). I think that the journal output is helpful, but flooding system's /var/log/messages is less than ideal. Should we disable this by default and let users enable the journal logging when they want on rhel-7?

Attachments

Issue Links

links to

RH BZ 1466862

Activity

People

Assignee:: Coty Sutherland

Reporter:: Coty Sutherland

Tester:: Jan Onderka

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2017/06/30 10:50 AM

Updated:: 2022/09/08 2:34 PM

Resolved:: 2019/07/26 9:50 AM