[hibernate-dev] Hibernate 4.0 logging looks too verbose still (suggest changing more info to debug/trace)

Scott Marlow smarlow at redhat.com
Mon May 16 11:37:21 EDT 2011


For another important warning (23:43:41,198 WARN 
[org.hibernate.cfg.AnnotationBinder] (MSC service thread 1-3) 
HHH00194:Package not found or wo package-info.java), I ran a debugger to 
find the call stack:  http://pastie.org/1911031


On 05/14/2011 12:37 AM, Scott Marlow wrote:
> Hi,
>
> The following Hibernate log output is from running the AS 7.0
> integration testsuite (with Hibernate 4.0.0.Alpha3)
> http://pastie.org/1899179
>
> I think some of the warnings might be telling me that we have something
> wrong in the AS7/Hibernate integration.  For example "23:43:42,001 WARN
>    [org.hibernate.ejb.AbstractEntityManagerImpl] (RMI TCP
> Connection(2)-127.0.0.1) HHH00326:Cannot join transaction: do not
> override hibernate.transaction.factory_class".  If so, we should fix the
> problem.
>
> I think it would be in the spirit of our logging guideline
> http://community.jboss.org/wiki/HowtologinJBossprojects, to move some of
> the (non-critical) INFO messages to DEBUG or TRACE.
>
> No one has disagreed about this in the past and many messages have
> already changed.  I wanted to see if we agree that more INFO messages
> should be changed to DEBUG/TRACE.
>
> For example, I think that we should use debug/trace level for indicating
> when a connection is obtained/released (since that is a normal operation
> that means that stuff is working).
>
> Scott
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev




More information about the hibernate-dev mailing list