Re: Logging Best Practices on RHEL

2013-12-03 Thread Konstantin Kolinko
2013/11/30 Christopher Schultz : > > On 11/27/13, 5:00 PM, Tomcat Random wrote: > >> "I find java.logging to be... frankly frustrating to configure." >> Totally agree, I feel like the Tomcat logging.properties file is >> weirdly clunky. > > Yes. That's because out of the box it uses java.util.loggi

Re: Logging Best Practices on RHEL

2013-12-03 Thread Tomcat Random
Chris, thanks. That's good to know since I just implemented 1.2.17. On Mon, Dec 2, 2013 at 5:27 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Alec, > > On 12/2/13, 3:48 PM, Tomcat Random wrote: > > Thanks Chris, Are you usi

Re: Logging Best Practices on RHEL

2013-12-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 12/2/13, 3:48 PM, Tomcat Random wrote: > Thanks Chris, Are you using log4j 1.x or 2.beta? I've been using 1.x for quite a long time. I haven't looked much into the new version. I'd be surprised if it's a mind-blowing upgrade. :) - -chris

Re: Logging Best Practices on RHEL

2013-12-02 Thread Tomcat Random
Thanks Chris, Are you using log4j 1.x or 2.beta? On Fri, Nov 29, 2013 at 6:06 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Alec, > > On 11/27/13, 5:00 PM, Tomcat Random wrote: > > Thanks Dave, I'll take a look at it. > > >

Re: Logging Best Practices on RHEL

2013-11-29 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 5:00 PM, Tomcat Random wrote: > 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 config

Re: Logging Best Practices on RHEL

2013-11-27 Thread Tomcat Random
...@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 >

RE: Logging Best Practices on RHEL

2013-11-27 Thread Dale Ogilvie
hich 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

Re: Logging Best Practices on RHEL

2013-11-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 12:35 PM, Tomcat Random wrote: > Yes, Yuk indeed. > > So just to clarify, you recommend using log4j, and replacing all > my printStackTrace with log4j specific code. Would that be > correct? It's really a matter of personal pref

Re: Logging Best Practices on RHEL

2013-11-27 Thread Tomcat Random
Yes, Yuk indeed. So just to clarify, you recommend using log4j, and replacing all my printStackTrace with log4j specific code. Would that be correct? Cheers, Alec On Wed, Nov 27, 2013 at 12:18 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- >

Re: Logging Best Practices on RHEL

2013-11-27 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Alec, On 11/27/13, 11:45 AM, Tomcat Random wrote: > 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. Yuk. > Could someone be so kind as to recom

Logging Best Practices on RHEL

2013-11-27 Thread Tomcat Random
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 gia