AbstractFlushingEventListener logs errors instead of just throwing an exception
-------------------------------------------------------------------------------

          Key: HHH-3433
          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3433
        Project: Hibernate3
      Issue Type: Bug
  Affects Versions: 3.2.5
       Reporter: Ryan Stewart
       Priority: Minor


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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

   
_______________________________________________
hibernate-issues mailing list
hibernate-issues@(protected)
https://lists.jboss.org/mailman/listinfo/hibernate-issues