> From: D. Barnhoorn [mailto:d.barnho...@tfe.nl] > Subject: Servlet silently dropped > > One of those servlets stops handling or maybe even > getting requests that it has a mapping for.
What does a thread dump show in this situation? > What is odd is that: > - it's always the same one Which narrows your focus considerably. > - tomcat serves a page for the url, but one from the main servlet So it appears the mapping is altered? The only dynamic mapping I'm aware of in Tomcat is for JSPs; are you using them anywhere? > - destroy() doesn't get called, so it either escapes the gc > or gets dropped without any fuss The destroy() API won't be called unless the entire webapp is stopped, which doesn't appear to be happening. > - creating a second mapping for the servlet returns the same > page How do you do that? The only way I'm aware of is to update web.xml, which will reload the entire webapp. > I did think of out of memory, threads, sockets stuff, but > you'd expect tomcat to at least log something like that Tomcat can't log anything when a thread hangs inside a servlet. Again, get a thread dump (or several). - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
