struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas (JIRA)" <>
Subject [jira] [Commented] (WW-4191) Excessive 404 error logging
Date Fri, 06 Sep 2013 05:02:52 GMT


Nicholas commented on WW-4191:

I have used the unknown handler management for more complex scenarios such as managing resources
from a CMS that were hosted on an external provider that are referenced relatively. Surely
straight out of the box struts shouldn't be producing exceptions for something that really
is not an exceptional case? It seems extremely overkill to have to write your own especially
when its producing a 404 output already (99% of what a web application wants to do).

The 'solution' is more of a work around for a fix that was put into place for a ticket that
was supposed to be in dev mode only anyway. Our applications have been running with more or
less the same setup since early webwork days...

> Excessive 404 error logging
> ---------------------------
>                 Key: WW-4191
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter
>    Affects Versions:
>         Environment: Redhat Linux, tomcat 6, Sun JDK 1.6
>            Reporter: Nicholas
>            Priority: Minor
>              Labels: logging
> During a recent struts upgrade that we did for security purposes we started receiving
large amounts of error logging when a visitor uses a URL that doesn't have an associated action
mapping (like a 404). This happens when debug mode is disabled.
> I believe the problem started when this JIRA ticket was 'fixed':
> I think the two commits giving us grief are:
> The error I'm receiving is:
> {noformat}
> ERROR org.apache.struts2.dispatcher.Dispatcher  - Exception occurred during processing
request: There is no Action mapped for namespace [/package] and action name [missingactionname]
associated with context path [/app].
> There is no Action mapped for namespace [/package] and action name [missingactionname]
associated with context path [/app]. - [unknown location]
> 	at com.opensymphony.xwork2.DefaultActionProxy.prepare(
> 	at org.apache.struts2.impl.StrutsActionProxy.prepare(
> 	at org.apache.struts2.impl.StrutsActionProxyFactory.createActionProxy(
> 	at com.opensymphony.xwork2.DefaultActionProxyFactory.createActionProxy(
> 	at org.apache.struts2.dispatcher.Dispatcher.serviceAction(
> 	at
> 	at
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> 	at com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(
> 	at com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(
> 	at org.apache.catalina.core.StandardContextValve.invoke(
> 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
> 	at org.apache.catalina.core.StandardHostValve.invoke(
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(
> 	at org.apache.catalina.authenticator.SingleSignOn.invoke(
> 	at org.apache.catalina.core.StandardEngineValve.invoke(
> 	at org.apache.catalina.ha.tcp.ReplicationValve.invoke(
> 	at org.apache.catalina.connector.CoyoteAdapter.service(
> 	at org.apache.coyote.http11.Http11AprProcessor.process(
> 	at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(
> 	at$
> 	at
> {noformat}
> For the moment we've simply set the log level for the effected class to none to get around
this but I don't think this is the optimal solution.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message