We chose slf4j with log4j underneath.
1. slf4j has nice optimal syntax:
Log.debug("The logged in user is {} {}",firstName,lastName);
http://www.slf4j.org/faq.html#logging_performance
2. It has bridging apis to route other logging frameworks. If you are
using other libraries which use a different logging framework, you could
capture these logs via a bridge.
http://www.slf4j.org/legacy.html
Dale
-----Original Message-----
From: Tomcat Random [mailto:tomcat.ran...@gmail.com]
Sent: Thursday, 28 November 2013 5:45 a.m.
To: Tomcat Users List
Subject: Logging Best Practices on RHEL
I'm running Tomcat 7.0.42 on RHEL. Currently all my exceptions are
handled with e.printStackTrace() and go to catalina.out, which doesn't
rotate.
Could someone be so kind as to recommend a better way to handle logging,
with specific steps. Daily error logs would be a good start, instead of
one giant catalina.out file.
Best,
Alec
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
