[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2971) AbstractFlushingEventListener catches, logs and re-throws HibernateException in performExecutions generating noisy logs
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2971?page=c...
]
Paulo Ricardo Ribeiro commented on HHH-2971:
--------------------------------------------
As Thomas S said, if we have external costumers, it's a bad thing for them to see
those logs, when it is not an actual appication error.
Stack traces shouldn't appear on logs, because on most of the times that means that an
unexpected exception occured;
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira