Using Hibernate 3.2.5.ga, the AbstractFlushingEventListener logs errors from line 301 in the performExecutions method any time a HibernateException is thrown within the method. The exception is then propagated upward. In some cases, client code will catch this exception and handle it, and the result is not considered an error. Then Hibernate has incorrectly made an error entry in the logs, which might have spawned an alert email or, worse, woken someone up at 2 AM with a page. Since the exception is propagated upward, there is no reason for Hibernate to log anything at this point. It should be left to client code to decide what to do with it.
Bulk closing stale resolved issues