Thanks Dave, I'll take a look at it.
Chris, thanks as well. Out of curiosity, do either of you know if/how you'd
consolidate logging for things like say clustering. I have clustering
configured for two physical servers each running an instance of tomcat. I
have logging configured as per the clustering docs, and it works, but I'm
not clear on how it would be reported by log4j, instead of JULI.
"I find java.logging to be... frankly frustrating to configure." Totally
agree, I feel like the Tomcat logging.properties file is weirdly clunky.
Cheers,
Alec
On Wed, Nov 27, 2013 at 3:34 PM, Dale Ogilvie <dale_ogil...@trimble.com>wrote:
> 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
>
>
