log4j and jsf

Well, i always use this:

log4j.logger.org.apache=INFO

log4j.logger.org.hibernate=DEBUG

//log4j.logger.net.sf=DEBUG

// no more debug from faces

//log4j.logger.javax.faces=DEBUG

log4j.logger.net.pimpas=DEBUG

CasMeirona at 2007-7-8 11:50:11 >

This is a log4j properties file problem. I'm not used to using the .properties file notation. I'm used to the XML notation for log4j.

Here's how I'd do it in XML:

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/'>

<!--

Set up the appender

-->

<appender name="Appender" class="org.apache.log4j.ConsoleAppender">

<param name="Append" value="true"/>

<layout class="org.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="%d{HH:mm:ss} %-5p %m%n"/>

</layout>

</appender>

<logger name="my.java.package" additivity="false">

<level value="debug" />

<appender-ref ref="Appender" />

</logger>

<logger name="another.package.for.debug.level" additivity="false">

<level value="debug" />

<appender-ref ref="Appender" />

</logger>

<!--

Omitting the JSF package altogether should remove the undesired

DEBUG messages from it. However, if not, uncomment the following

lines.

-->

<!-- <logger name="javax.faces" additivity="false">

<level value="INFO" />

<appender-ref ref="Appender" />

</logger> -->

<root>

<priority value ="debug" />

<appender-ref ref="Appender" />

</root>

</log4j:configuration>

This example will print to console only. If you want to print to a file instead, use the following lines (replaces the appender tags from the above example).

<appender name="Appender" class="org.apache.log4j.DailyRollingFileAppender">

<param name="File" value="filePath/FileName.log"/>

<param name="DatePattern" value="'.'yyy-MM-dd"/>

<param name="Append" value="true"/>

<layout class="org.apache.log4j.PatternLayout">

<param name="ConversionPattern" value="%d{HH:mm:ss} %-5p %m%n"/>

</layout>

</appender>

I don't know how you'd get both the console and the file appender working at the same time.

If you want further advice, or If you want advice on the .properties method of doing things, I suggest finding a log4j forum. The people there will undoubtedly have more experience and knowledge than us JSF nerds. =)

I assure you though, JSF is compatible with log4j. The log4j properties file just needs to be set up properly (more challenging than it should be, if you ask me).

CowKing

IamCowKinga at 2007-7-8 11:50:11 >

I tried all your suggestions again I have debugs that I don't need.

My log4j.properties is:

log4j.rootLogger=debugLog, stdout

# CONSOLE appender

log4j.appender.stdout=org.apache.log4j.ConsoleAppender

log4j.appender.stdout.layout=org.apache.log4j.PatternLayout

log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss} %-5p %m%n

log4j.appender.debugLog=org.apache.log4j.DailyRollingFileAppender

log4j.appender.debugLog.Threshold=debug

log4j.appender.debugLog.layout=org.apache.log4j.PatternLayout

log4j.category.com.corejsf = debugLog

log4j.category.org.apache.commons=ERROR

log4j.category.org.apache.struts=ERROR

### Enabling debug logging for jsf-ri implementation of Lifecycle only ###

log4j.logger.com.sun.faces.lifecycle.LifecycleImpl=DEBUG

log4j.com.sun.faces=ERROR

Still I have too many debugs such as:

10:38:10 DEBUG addConverterByClass(float,javax.faces.convert.FloatConverter)

10:38:10 DEBUG added converter of class type javax.faces.convert.FloatConverter

10:38:10 DEBUG addConverterByClass(int,javax.faces.convert.IntegerConverter)

10:38:10 DEBUG added converter of class type javax.faces.convert.IntegerConverter

10:38:10 DEBUG addConverterByClass(long,javax.faces.convert.LongConverter)

10:38:10 DEBUG added converter of class type javax.faces.convert.LongConverter

10:38:10 DEBUG addConverterByClass(short,javax.faces.convert.ShortConverter)

juanitaJa at 2007-7-8 11:50:11 >

JuanitaJ:

I had the same problem as you, but finally figured it out!

the problem is that you (and I) define a rootLogger in the log4j.properties file.

This is the parent of all other loggers including loggers defined in the JSF components.

Instead of declaring:

log4j.rootLogger=DEBUG, destConsole, destFile

I now declare an app-specific logger to be the parent of all loggers I use in my project:

log4j.logger.jsf_db=DEBUG, destConsole, destFile

In java I set up my logger as a child of this logger:

import org.apache.log4j.Logger;

..

..

private Logger logger = Logger.getLogger("jsf_db." + this.getClass());

my complete lo4j properties file is:

#log4j.rootLogger=DEBUG, destConsole, destFile

log4j.logger.jsf_db=DEBUG, destConsole, destFile

log4j.appender.destConsole=org.apache.log4j.ConsoleAppender

log4j.appender.destConsole.layout=org.apache.log4j.PatternLayout

log4j.appender.destConsole.layout.ConversionPattern=%d %-5p %-5c{3}:%L %x -> %m%n

log4j.appender.destFile=org.apache.log4j.RollingFileAppender

log4j.appender.destFile.MaxFileSize=2500KB

#log4j.appender.destFile.File=D:\\data\\projects\\JSF\\jsf_db\\webRoot\\log\\jsf_db.log

log4j.appender.destFile.File=/data/projects/jsf_db/webRoot/log/jsf_db.log

log4j.appender.destFile.layout=org.apache.log4j.PatternLayout

log4j.appender.destFile.layout.ConversionPattern=%d %-5p %-5c{3}:%L %x -> %m%n

TheRealLocutusa at 2007-7-8 11:50:11 >

But I thought to inherit from the parent made log4j so interesting,

now you cannot change the log-level system-wide with

just 1 change in the log4j properties file.

Now you have to set the level of every logger you create in your code.

At the risk of being boring I will explain what I did:

"jsf_db" is just a name, it happens to be the name of my application,

but you can just as well choose: "any_root_name_you_like".

so you can declare in the properties file:

log4j.logger.any_root_name_you_like=DEBUG, appender1 appender2

In my application I have many classes, in every class I define:

private Logger logger = Logger.getLogger("any_root_name_you_like." + this.getClass());

which gives me a loggernamed "any_root_name_you_like.className"

which is a child of "any_root_name_you_like" and thus inherits it's level from it.

Now I still can change my applications logtlevel with 1 change in the properties file.

By the way, using this.class() tells me directly where the logged event ocurred.

TheRealLocutusa at 2007-7-21 16:24:29 >