]
Andreas Bergander commented on HHH-2971:
----------------------------------------
I agree with craig.
In a production environment it is of importance to have clean logs so no false alarms are
triggered in a log monitoring application. To always log this on error-level seems like a
bad idea. Let the application catch the re-thrown exception and choose whether or not this
should be logged.
Anyone else thinks that this issue should be re-opened?
AbstractFlushingEventListener catches, logs and re-throws
HibernateException in performExecutions generating noisy logs
-----------------------------------------------------------------------------------------------------------------------
Key: HHH-2971
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2971
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.5
Environment: v3.2.5
Reporter: craig mcmillan
Assignee: Diego Plentz
Priority: Minor
Attachments: tags.v325.r14204.patch
AbstractFlushingEventListener catches HibernateException, logs an error, and re-throws
the same HibernateException... so the Exception gets logged twice, or worse [ in the case
i'm looking at, an offline locker ], an expected Exception
[ConstraingViolationException] is caught and discarded, but an error is still logged
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: