|
From: Trevor C. <pr...@se...> - 2003-09-27 18:21:27
|
I have a bit of a problem with the DispatcherServlet's doService method,
specifically:
if (mappedHandler == null || mappedHandler.getHandler() == null) {
// if we didn't find a handler
logger.error("No mapping for [" + WebUtils.getRequestUri(request) + "] in
DispatcherServlet with name '" + getServletName() + "'");
response.sendError(HttpServletResponse.SC_NOT_FOUND);
return;
}
I think the 404 is fine (I noticed the previous thread for multiaction on
this - see http://sourceforge.net/mailarchive/message.php?msg_id=5986871).
My problem is "logger.error". I have log4j send me anything above info for
my code, and anything error/fatal for Spring. Because of this, I am
currently getting dozens of emails a day from spiders, spelling errors, and
1 site that refuses to change a bad link on their page. I considered just
changing my logging to only report fatal errors from Spring, but Spring
doesn't have any, and other errors it reports are important (like
transaction and configuration problems). I'd like to change this from error
to warn. "warn" is defined as:
<quote>other runtime situations that are undesirable or unexpected, but not
necessarily "wrong".</quote> see
http://jakarta.apache.org/commons/logging/userguide.html
I think that a 404 is not a desirable thing, but is fairly normal for a
webapp, so falls under the "not wrong" category.
Let me know if there is general support for lowering the logging level of
this message, or if I'm totally out to lunch.
Trevor D. Cook
|