Hibernate uses Commons Logging to control its log messages. It logs at INFO level by default, so there must be a configuration somewhere else in your application which is asking for log levels at TRACE. Look at the class the log method is being made from (should be included in the log message) - is it a Hibernate class? It depends which logging framework you are using as to where a config. file will be, if its log4j then log4j.properties will be on your classpath somewhere. If its JDK logging its JAVA_HOME/jre/lib/logging.properties.
Thanks for the info. It looks like my app is using standard JDK logging. I tried to implement log4j, but was not succesful. I tried to add the log4j jar file in my WEB-INF/lib and my Spring Beans would not load any longer. Tomcat complains that it could not find the bean classes. I am assuming some library that log4j uses is breaking down which may be caused by some CLASSPATH issues introduced when I added log4j. Does this make sense? Anybody ever deal with this issue?