On 10/05/2012 16:57, Jesse Farinacci wrote: > Greetings, > > On Thu, May 10, 2012 at 11:41 AM, Mark Thomas <ma...@apache.org> wrote: >> The thing that doesn't make sense yet is that Tomcat is trying to read from >> a WAR (or possibly a JAR) but the app should be unpacked. With that in mind: >> - requests for what resources trigger this problem? >> - where is that resource located in the unpacked application? >> - are you making use of Servlet 3.0 resource JARs. > > Your instinct is quite good. Yes, that is exactly where the error is > happening. I narrowed it down to our WEB-INF/lib/common-favicon.jar > which has (among other automatically generated Maven junk): > > META-INF/resources/ > META-INF/resources/favicon.ico > META-INF/resources/images/ > META-INF/resources/images/favicon.ico > > Legacy reasons for the duplicated paths, please ignore this > idiosyncrasy. But, we take HTTP-500 when trying to fetch the > favicon.ico image directly, both paths. The stack trace I reported > before is generated each time. > > Given this insight, thank you, I don't think that this is the cause > for delay and I will investigate outside of Apache Tomcat for the root > cause.
I've had a good look at the code and I can't see anything that jumps out as the cause of this. Does this happen as soon as Tomcat starts, after a while, after a reload, after something else? Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
