[ http://opensource.atlassian.com/projects/hibernate/browse/HB-1363?page=co... ] Chris Lee commented on HB-1363: ------------------------------- Please remove this error from the exception constructor; it should be up to the developer to control if/when/where they want to log exceptions (i.e. it should not be forced on them). In our case, we have a diagnostics filter that outputs web request and session attributes - this filter is run *after* an open session in view filter, ergo we are expecting LazyInitializationExceptions (which are ignored) - except that our logs are polluted with useless log messages. While we could reconfigure log4j for this, it seems silly to do supress something that shouldn't be output in the first place. -- 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