Hi Konstantin, You are right it's one of the auxiliaries, forgot to add that. The init() completes, the servlet will also work for an indefinite amount of time - if we're lucky right up till the next update of the site. Otherwise we have too restart Tomcat to get the servlet up and running again. It's a load balanced environment (4 servers, no session sharing) so it is mostly just annoying for the guys in the server department who have to restart the tomcat when it occurs. So far I haven't been able to trigger something that could be used to signal the failure (which would make it possible to trigger a scripted response) or to get rid of it (which of course is preferable :))
danny Konstantin Kolinko wrote: > > I understand that it is one of those 28 auxiliary servlets. > > Does its init() complete cleanly? > > If it does not, the container must drop the servlet instance, and the > destroy() > method is not called. See the chapter SRV.2.3.2.1 from the servlet spec > 2.4. > -- View this message in context: http://www.nabble.com/Servlet-silently-dropped-tp21541015p21542288.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
