Hi, We have a strange problem at one of our clients in that Tomcat seems to drop a specific servlet while running. This happens very sporadically and is possibly connected with a high load.
The server is a Sun sparc running Tomcat 5 in java 1.4.2_02 The application is based around one servlet that takes almost all the requests and several small ones with various specific tasks (29 servlets in all, all except for the main ones with a very specific mapping). One of those servlets stops handling or maybe even getting requests that it has a mapping for. What is odd is that: - it's always the same one - tomcat serves a page for the url, but one from the main servlet - destroy() doesn't get called, so it either escapes the gc or gets dropped without any fuss - creating a second mapping for the servlet returns the same page, so while it's running the right one and once the original mapping doesn't work anymore the extra mapping doesn't work either - absolutely no logging of anything that might give me a clue; I did think of out of memory, threads, sockets stuff, but you'd expect tomcat to at least log something like that Anyone seen something like this before? Or some pointers where I might be able to trace this to the root? It only happens on the live server of course - and only sporadically at that, so having a debugger open is kind of out of the question :( Any ideas will be welcome :) Thanks in advance, danny -- View this message in context: http://www.nabble.com/Servlet-silently-dropped-tp21541015p21541015.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
