tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felipe Schnack <feli...@ritterdosreis.br>
Subject Re: HttpProcessor not recycling connections / bug 5181 ?
Date Fri, 25 Oct 2002 11:22:13 GMT
  Wow, asking to upgrade to 4.1.x to solve a bug isn't just too much?
Personally I'm waiting 4.1.x to get more stable before upgrading it.

On Fri, 2002-10-25 at 09:21, Remy Maucherat wrote:
> Graham King wrote:
> 
> >     Dear all,
> >
> >  I'm running Tomcat 4.0.3 with Java 1.4 on Linux, and we are getting
> > lots of 'IOException: Connection reset by peer' (see stack trace at
> > bottom of mail), which I understand is the user hitting 'stop' or
> > closing the window before the load completes.
> >
> > After several hours of running our server will run out of request
> > processors (well actually we put maxProcessors at 1024 so the site falls
> > over with 'OutOfMemoryError: unable to create native thread' but that's
> > just whilst we try and fix this).
> >
> > I believe this is because StandardWrapperValve is catching the
> > IOException, so it never gets back up to HttpProcessor, so the processor
> > never gets recycled.
> >
> > I saw in a comment right at the bottom of here
> > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5181 that this is
> > fixed in 4.0.4b1, but I could not find any other information about that
> > in the release notes, bugzilla or mail list archives.
> >
> >  We can't use the 4.1.X branch because we symlink to content outside the
> > webapp directory and the allowLinking doesn't work for us (in 4.1.12 at
> > least).
> >
> >  So what I am asking is:
> >
> >  - Does anyone know of a recorded problem with recycling processors in
> > 4.0.3 and if so is this definately fixed in later versions of 4.0.X ?
> >  And:
> >  - Has anyone else experienced something like this and is my analysis
> > way off mark ?
> 
> Mmmm, yes, it's kinda bogus. A case where a processor wouldn't be 
> recycled is if an exception is *not* caught (the thread would get 
> killed). There's still a hypothetical bug with recycling of the 
> processors that has been reported once in a while, but that no committer 
> has ever been able to reproduce, except in conjunction with garbage 
> collection peaks.
> 
> You should reorganize your setup to make your webapps look like real 
> webapps, and upgrade to 4.1.x.
> 
> Remy
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>
> 
-- 

Felipe Schnack
Analista de Sistemas
felipes@ritterdosreis.br
Cel.: (51)91287530
Linux Counter #281893

Faculdade Ritter dos Reis
www.ritterdosreis.br
felipes@ritterdosreis.br
Fone/Fax.: (51)32303328


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message