Avoid stack trace logging when portal page not found

16111
Reporter: mdoering
Type: Bug
Summary: Avoid stack trace logging when portal page not found
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2014-07-11 17:53:47.72
Updated: 2017-10-09 17:15:39.698
Resolved: 2017-10-09 17:15:39.672
        
Description: When an action throws the NotFoundException the standard struts exception mapper logs a stacktrace which is cluttering logs. Just log one line instead.

www.gbif.org/species/124458707

For example ERROR [2014-07-11 17:49:48,467+0200] [http-bio-8080-exec-615] com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor: No usage found with id 124458707
org.gbif.portal.exception.NotFoundException: No usage found with id 124458707
]]>