Turn off the debug logging for Trinidad

[Ray Daniel <bu...@gmail.com>]

This is killing my production server at the moment with 100+meg log files
each day. How do I properly squelch these? I see thousands of lines of each
phase being logged...

31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Filter request output to XML
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - XML filter service start processing request
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Process before phase RESTORE_VIEW(1)
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Process after phase RESTORE_VIEW(1)
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Process before phase RENDER_RESPONSE(6)
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - PhaseListener enter Before RenderView Phase with
ViewId /jsp/login/login.jsp and RenderKitId org.apache.myfaces.trinidad.core
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Save State of UIAjaxComponent with Id _viewRoot
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Create StringWriter for buffer servlet output
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Create StringWriter for buffer servlet output
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Process component tree for collect used scripts and
styles
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Process after phase RENDER_RESPONSE(6)
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - create HTML/XML parser for content type: text/html
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Parsing html total time 0ms
31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger (
Log4JLogger.java:84) - Finished request processing total time 79ms for uri:
/ccm/jsp/login/login.jsf

Re: Turn off the debug logging for Trinidad

[simon <si...@chello.at>]

On Fri, 2007-08-31 at 15:03 -0500, Ray Daniel wrote:
> This is killing my production server at the moment with 100+meg log
> files each day. How do I properly squelch these? I see thousands of
> lines of each phase being logged...
> 
> 31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger
> (Log4JLogger.java:84) - Filter request output to XML
> 31 Aug 07 00:01:37, DEBUG [TP-Processor14] impl.Log4JLogger
> (Log4JLogger.java:84) - PhaseListener enter Before RenderView Phase
> with ViewId /jsp/login/login.jsp and RenderKitId
> org.apache.myfaces.trinidad.core
> 
Weird. The logging category is presumably
  org.apache.commons.logging.impl.Log4JLogger

The messages do appear to be coming from either MyFaces or Trinidad,
based upon the content of the messages.

I would guess that code somewhere is doing this:

  Log log1 = LogFactory.getLog(Foo.class);
  Log log2 = logFactory.getLog(log1.getClass());
  log2.log("Filter request output to XML");

This would be a pretty silly thing for code to be doing, but I cannot
think of any other code that could cause messages with category of
"...impl.Log4JLogger".

Ray, the immediate fix for you is obviously to just change your log4j
configuration file to not output DEBUG messages for category
"impl.Log4JLogger". Log4j's default config is to not log anything so
someone at your site must have explicitly enabled debug logging output.
See log4j documentation for information on configuring log4j.

Regards,

Simon

Re: Turn off the debug logging for Trinidad

[DRAY <bu...@gmail.com>]

No worries. I just wasn't sure if I missed something obvious in a config file
somewhere. Many thanks for the quick response.
-- 
View this message in context: http://www.nabble.com/Turn-off-the-debug-logging-for-Trinidad-tf4363669.html#a12510738
Sent from the MyFaces - Users mailing list archive at Nabble.com.