[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-647) Don't log duplicate key exceptions as an ERROR

[Jonathan Amir (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35132#action_35132 ] 

Jonathan Amir commented on HHH-647:
-----------------------------------

Bug 3731 seems to be the same as this one. Regarding Gavin's comment, unfortunately it is not possible to suppress this logger category, it is a solution that is too extreme because the message is logged at level ERROR. Please see details at the other bug report.

> Don't log duplicate key exceptions as an ERROR
> ----------------------------------------------
>
>                 Key: HHH-647
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-647
>             Project: Hibernate Core
>          Issue Type: Improvement
>         Environment: Hibernate 3.0.5, MySQL
>            Reporter: Jeantine Michelle Mankelow
>            Priority: Minor
>
> Hibernate is logging duplicate key exceptions logged as ERROR.
>  
> Our application handles errors of this kind and turns them into validation messages for the user, as I imagine is the case for many other applications.  
> It is a concern for us that this appears in the log as an error when it is not, it may cause undue concern for our clients, at the very least it will clutter the log.  We would rather this type of exception is not logged, or at the very least should be scaled down to the INFO or WARNING class. 

-- 
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