[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2971?page=c...
]
Markus Merder commented on HHH-2971:
------------------------------------
This issue also affects version 3.3.1. I think the priority should be more than minor, as
many production environments are monitored and should not log errors that are no errors.
for example you could get a StaleObjectStateException in case you use optimistic locking.
This is a common case in multi-user environments and should not cause a log if you catch
that exception.
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:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira