I'm experimenting with Hibernate 2.1 in a stand-alone application running on Netbeans.

I am trying to turn on log4j logging, unsuccesfully. I have log4j.jar and log4j.properties on my classpath. I am able to use logging in my own code, and affect its behaviour by settings in the log4j.properties file. I cannot turn on logging for the log4j code however.

Here are the contents of log4j.properties

### direct log messages to stdout ###
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L - %m%n

log4j.rootLogger=debug, stdout
log4j.logger.net.sf.hibernate=debug
log4j.logger.net.sf.hibernate.type=debug
log4j.logger.net.sf.hibernate.tool.hbm2ddl=debug
log4j.logger.mystuff=debug

My code, in package mystuff is using logging no problems.

Any ideas??

Thanks for your help
Jairaj

Hibernate use commons-logging, so you must tell this wrapper to use log4j, setting this property:

Ciao.

Thanks for the help

I created the property in the hibernate.cfg file. That didn't work. Where should I create the property?

I thought commons-logging worked out whether to use log4j or jdk1.4 logging for itself, by checking for log4j on the classpath.

Thanks again,
Jairaj

With -D as JVM parameter.
Ciao.

Ok I created a commons-logging.properties file.

Now I get a ClassNotFoundException for org.apache.commons.logging.impl.Log4JCategory

I used
org.apache.commons.logging.log=org.apache.commons.logging.impl.Log4JCategoryLog

That works now, thanks.

Anywat I think that putting it into the hibernate.cfg.xml would be a good idea !!!
Ciao.

As per the commons-logging documentation, this should not be required: by default commons-logging switch to Log4J if found in the classpath...

I disagree, Hibernate isn't the only framework using commons-logging. having it's config in Hibernate config would sucks.

Actually commons-logging does choose log4j if it is on the classpath. My problem was caused by having ws-commons-logging.jar (Websphere library) on the classpath (for some reason) which messed things up.

So it was ..err.. IBM's fault! Anyway using org.apache.commons.logging.log=org.apache.commons.logging.impl.Log4JCategoryLog did work for this situation when put in a commons-logging.properties file.

This may be a solution if trying to deploy to Websphere.

Poeple I know using Websphere, replaced the ws-commons-logging.jar by an appropriate commons-logging one.

IBM addressed this issue in the current or future release.

I am also trying to turn logging on in WebSphere for hibernate.

I have placed both the commons-loggin.properties file and log4j.properties file in my classpath but the configurations don't seem to change anything. I am still at the INFO level.

I tried replacing the ws-commons-logging.jar file with the latest commons version but get an error when I start up the built in WAS 5.0 server:



So, I have to put it back to work. Any ideas how to get this to work? I am trying to make this work so that I can trouble shoot a different hibernate problem I already posted about.

Hi, I had a PMR for this at one point with IBM> We use the "PARENT_LAST" classloader scheme, and had issues with commons-logging from websphere. By default, was5 uses PARENT_FIRST classloader, which means classloader will attempt to use was stuff first. Instead of replacing the was logging jar, just use PARENT_LAST. In addition, in order to prevent commons-logging from finding commons-logging.properties from the WAS version of the file, simply put a blank file called "commons-logging.properties" in your classpath.

We use log4j, and have no problems when we use this approach.
You will need log4j.properties on your classpath too.

Hope this helps.

James