You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Keith Wannamaker <Ke...@Apache.org> on 2004/10/15 16:42:21 UTC

Tomcat 5.0 under load

Last month I took Yoav's advice and attempted to upgrade our production 
server from 4.1 to 5.0.  The production server handles 5 - 10 requests a 
second across 300 threads.  The problem I had then, and the problem I 
have now is that the server's accept thread will die within a short time 
after server start.  I hate to think I am the only person running tomcat 
5 under a heavy load, but it sure looks that way.

I initially blamed threadpool's bulletproofing, but because 4.1.31 and 
5.0.28 share the same threadpool, and 4.1.31 runs indefinitely, there is 
a problem in core 5.0 that this load is exercising.

I very much want to be able to recommend that tomcat 5.0 is 
production-ready but since we can't run it, I certainly am not in a 
position to do that.  I have reserved the next day or two for 
bulletproofing tomcat 5.0, so the point of this is to solicit any 
comments from those who may have been faced with the same problem and 
have looked at the problem themselves.

Thanks for any input,
Keith


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Re: Tomcat 5.0 under load

Posted by Remy Maucherat <re...@apache.org>.
Keith Wannamaker wrote:

> Last month I took Yoav's advice and attempted to upgrade our 
> production server from 4.1 to 5.0.  The production server handles 5 - 
> 10 requests a second across 300 threads.  The problem I had then, and 
> the problem I have now is that the server's accept thread will die 
> within a short time after server start.  I hate to think I am the only 
> person running tomcat 5 under a heavy load, but it sure looks that way.
>
> I initially blamed threadpool's bulletproofing, but because 4.1.31 and 
> 5.0.28 share the same threadpool, and 4.1.31 runs indefinitely, there 
> is a problem in core 5.0 that this load is exercising.
>
> I very much want to be able to recommend that tomcat 5.0 is 
> production-ready but since we can't run it, I certainly am not in a 
> position to do that.  I have reserved the next day or two for 
> bulletproofing tomcat 5.0, so the point of this is to solicit any 
> comments from those who may have been faced with the same problem and 
> have looked at the problem themselves. 

First, I didn't see any previous message about any of your problems.

Then, why do I even have to ask which OS / VM / connector / etc you are 
running ? Also mention exactly what the "server's accept thread will 
die" mean.

BTW, jboss.org is running on Tomcat 4.1 (inside JBoss), with more load 
than your site, on RedHat EL 3 (we did have many issues on RH 9 that 
LD_ASSUME_KERNEL solved in a large part). Except when we're making a 
configuration mistake (it happens more often than I would like), we 
don't have many issues (we do have annoyance of TC 4.1 compared to 5.0 - 
we'll upgrade soon, I am being told, so I'll let people know how well it 
goes).

Rémy


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org