Hi there,

i just updated my hibernate core to the new version and have really big trouble with the slf4j thing.

since i update the hibernate core and download the slf4j 1.5.2 library from their site, i get thousands of logging messages like:



i try to add a log4j.properties file and add this line:


But nothing changed...

Hope somebody can tell me how i can turn off all these info Messages cause it really annoys me a lot!

Thanks a lot and greetings from Germany!
Daniel

change the log-level of hibernate to ERROR or FATAL (or whatever you like):



i wouldnt suggest to completely turn of logging

I added this line, but nothing changed :-(

here is a config-file of mine:

Hi soulspirit,

i try to run it exactly with your config-file but the hibernate logging is still there .-(

Did i have to set anything else in my Code?
I try to do this, to get certain that he use the right file before anything else is calling:


but logging is still there ...

no i just have the log4j.properties in my output dir. make sure its copied there when building your application.

hmm ok i see that he found the properties file but it is really weird ...

i do a little test like this:



i can't see the test Message output cause it hat the INFO level. When i chage the code to:


i can see the output so the properties file seems to work.
But i still see the whole other output stuff ...
(maybe it is important that the annoying stuff is in red?!)

How did you turn it on. I cant get that to turn on. I have slf4j-api-1.5.3.jar, slf4j-log4j12-1.5.3.jar in the class path and I have:



in my log4j.xml. I am using dom configurator.

I can't run my application with only these 2 classes cause i need the "slf4j-simple-1.5.2.jar" from the slf4j project site to start the app.

I didn't turn on anything, i get these output after upgrading to new hibernate and inclusing this slf4j library :-(

Anybody who can helps me to put that stuff off? Thanks a lot!

Has anyone figured this out???? I am also having this issue. I have a log4j.properties file in my classpath and changing it alters log output from other parts of my application, but hibernate logs are unaffected. I also noticed that the format of the log statements are not the same as what log4j is using.

Is it possible that hibernate is trying to use some other logging here?

I also have log4j & slf4j in my classpath, but am only using log4j. However if I remove slf4j from the project, I get errors from hibernate that is trying to use slf4j.

This happens even if I set org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger to tell it to use log4j.

Ok, I found a solution. I had the slf4j common and log4j jars in the classpath. I removed the common one and it works correctly now.

Hello,

I dont have the common jar file that you said taking out would fix. I have the following in the same order.

antlr-2.7.6.jar
commons-collections-3.1.jar
dom4j-1.6.1.jar
javassist-3.4.GA.jar
jta-1.1.jar
hibernate3.jar
slf4j-jdk14-1.5.2.jar
log4j-1.2.15.jar
classes12.jar
slf4j-api-1.5.2.jar

Do you see any version descrepencies?

Thanks

I think you don't need slf4j-jdk14-1.5.2.jar. Instead, you should use slf4j-log4j12-1.5.2.jar if you are going to use log4j library (at least, you have the log4j jar).

Remember to use the same version for slf4j-api and slf4j-log4j, just in case...

If you remove slf4j-jdk14-1.5.2.jar and add slf4j-log4j12-1.5.2.jar you should be able to manage logging from the log4j.properties file.

I hope this helps.

Have ever figure out how to disable hibernate logging
I think I have the same issue?
I can control logging coming from my custom files by configuring log4j.xml placed in the root of my classpath.
Hibernate does not respond to any configuration changes in that file.
Please, help me to deal with this.

Luis_hibernate has it right..

SLF4J is used by hibernate and if you are using log4j you need to setup the bridge for your logging system.
http://www.slf4j.org/legacy.html

you will need the slf4j-api, but make sure you also have slf4j-log4j12-1.x.x.jar

Remember you can only have one bridge at a time so you may have to delete or exclude (for maven users) any other slf4j loggers (such as slf4jsimple)

hope this helps