Hi,

We're trying to capture the SQL statements created dinamically by Hibernate during execution with Log4J.

I confess I've just dropped into solving this problem but we're getting a very strange problem from what my friend has already done.

We're using a log4j.properties file and setting Log4J through it to print all messages into a log file.

We're using a certain test aplication as a test to this properties file. When we run the program, it prints no messages into the console but prints all of them and the sqls we need into the log file correctly.

Now, in our main application, using the very same properties file and the same log4j.jar file we get a different reaction.

It prints loads of stuff into the console and only prints into the log file the 2 debug lines I directly create in my code (something like: "This is a test.").

Both access the same database and do the same query.

What can be happening here? I don't see any explicit log4j configuration in any class overriding the properties file.

If someone can lead me into the kind of thing I should look for, I'd apreciate.

We're using Hibernate 3.

I believe that Hibernate uses commons-logging to do their logging. I had a similar problem when deploying on Websphere because IBM (in their infinite wisdom) decided that all commons-logging calls should use the JDK logger instead of any configured loggers. Check for commons-logging conflicts in your environment.

Just checked your post.

And my friend has just arrived here too. He reached the very same conclusion that you gave me by himself. So he came to me saying "Hey it works! It's because of..." and I just pointed your post to him. :P

Now it works!

Thanks!

Interceptor.prepareStatement()

So when you say "Check for commons-logging conflicts in your environment" what do you mean to check exactly?

Can someone please say clearly ( a little more details) on how to resolve the common-logging conflict on websphere to expose Hibernate log?

Here is a couple tips. Essentially, if you are trying to use log4j with WAS' commons-logging, it won't work out-of-the-box, a couple of tweaks to prevent this are delineated in the above link.

Personally, because of this, I use straight log4j and bypass commons-logging. I don't miss the one-off level of indirection that commons-logging provides.

Ananasi :

I solved my problem by going thru the link you posted. Thanks a lot for the help!