Hi!
Our logs are pretty filled up with loggings like this:
2009-09-02 15:24:32,462 ERROR [org.apache.catalina.core.ContainerBase.
[jboss.web].[localhost].[/].[default]] (ajp-127.0.0.1-8009-2)
Servlet.service() for servlet default threw exception
javax.servlet.ServletException: SiteLocatorFilter with no Site :-(
....[full stack trace]
This logging, including a full stack trace, appears if you try to
access a non existing resource:
http://myserver.com/foobar.txt
If you deploy different applications, you can be sure that there will
be some accessing to non existing resources. Maybe a browser tries to
lookup some icons etc, a resource could be missing from an app, people
are trying to do something odd with urls, etc, etc.
This has always been a "problem" for us, and I guess we're not alone
here.
Referring to the logging, this is a situation that sesat handles
properly. That's why I think the full stack trace should be removed.
Maybe the log level should be reduced to WARN as well.
Stack traces in logs is pretty serious in my point of view, and that's
not the case in this situation.
An even better logging could be:
WARN: Lookup of non existing resource, with no site: "foobar.txt"
I know that there are people agreing with me in this, so I hope that
this suggestion can be implemented.
Thanks :)
Endre Midtgård Meckelborg
Seniorutvikler ⁄ Scrum Master
FINN tjenester og bedrifter
Tlf: +47 93 01 45 04
[email protected]
Mulighetenes marked
Grensen 5-7
Pb. 747 Sentrum
0106 Oslo
Telefon: +47 22 86 44 10
Telefaks: +47 22 42 96 97
http://www.finn.no
_______________________________________________
Kernel-development mailing list
[email protected]
http://sesat.no/mailman/listinfo/kernel-development
