On Tue, Jul 04, 2006 at 09:19:53AM -0400, Javier Gonzalez wrote:
A possible fix is configuring the root Logger for DEBUG priority -
however, this will leave all loggers logging at DEBUG level.
I tried that too - still have seen no logs except logs for my application.
I
think it's because
On Mon, Jul 03, 2006 at 02:18:13PM -0400, Javier Gonzalez wrote:
You only have an appender attached to the root logger, and the root
logger is configured to show only messages of ERROR level and higher.
Right, but for org.apache.commons it is set to DEBUG.
A possible fix is configuring the
On 7/4/06, Eugeny N Dzhurinsky [EMAIL PROTECTED] wrote:
On Mon, Jul 03, 2006 at 02:18:13PM -0400, Javier Gonzalez wrote:
You only have an appender attached to the root logger, and the root
logger is configured to show only messages of ERROR level and higher.
Right, but for org.apache.commons
Message-
From: Eugeny N Dzhurinsky [mailto:[EMAIL PROTECTED]
Sent: Friday, June 30, 2006 9:43 AM
To: log4j-user@logging.apache.org
Subject: [SPAM (Bayesain Analysis)] - problems with logging -
Bayesian Filter detected spam
Hello!
I have strange problem with Log4J version 1.2.13
My
You only have an appender attached to the root logger, and the root
logger is configured to show only messages of ERROR level and higher.
A possible fix is configuring the root Logger for DEBUG priority -
however, this will leave all loggers logging at DEBUG level.
Another fix could be
Hello!
I have strange problem with Log4J version 1.2.13
My log4j.properties file looks like:
log4j.rootLogger=ERROR, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p
