: Tue, 20 Jan 2009 08:17:27 -0600
> Subject: RE: Servlet silently dropped
>
> > From: D. Barnhoorn [mailto:d.barnho...@tfe.nl]
> > Subject: RE: Servlet silently dropped
> >
> > Main servlet grabs /**
>
> I don't think "/**" is a valid mapping, if I
> From: D. Barnhoorn [mailto:d.barnho...@tfe.nl]
> Subject: RE: Servlet silently dropped
>
> Main servlet grabs /**
I don't think "/**" is a valid mapping, if I'm interpreting the servlet spec
properly. You should be using just "/" for your default
e servlet and the vm at the time it occurs.
>Tomcat can't log anything when a thread hangs inside a servlet. Again, get
a thread dump (or >several).
A hanging servlet would mean timeouts for the client I think? Or error 500?
danny
--
View this message in context:
> 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
er 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 th
2009/1/19 D. Barnhoorn :
>
> 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
ontext:
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 additi
