Dispatcher logs an error / severe from serviceAction() before it returns a 404
"Could not find action or result"
----------------------------------------------------------------------------------------------------------------
Key: WW-2874
URL: https://issues.apache.org/struts/browse/WW-2874
Project: Struts 2
Issue Type: Bug
Affects Versions: 2.1.2
Environment: Tomcat 6.0.18, Struts 2.1.2
Reporter: Lucas Nelson
We are getting severe logs from
org.apache.struts2.dispatcher.Dispatcher.serviceAction() (line 485) when broken
spiders hit our site with all-lowercase URLs. Our actions are named with the
usual camel-hump style naming, so the server is returning a 404 to the client.
This is all good.
But, just before it returns the 404, the Dispatcher logs at error level: "Could
not find action or result".
We are trying to get to the situation where we can have all severe / error logs
trigger an alert to wake someone up in the middle of the night to go look at
the system. Having client-initiated activity triggering logging at severe /
error level does not seem right.
Any chance this log at line 485 could be lowered to a warning, at least?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
