Hi, There are certainly other sites running Tomcat 5.0 under heavy load, such as the ones listed on our wiki. I personally have put Tomcat 5.0-based apps in production that have handled the load you describe (and much higher peak bursty loads) for months at a time without need to restart.
However, it could very well be your specific app or configuration is exercising parts of Tomcat in ways other apps aren't. Every app load profile is unique. So this should definitely result in an improvement to Tomcat, or maybe the connectors if you're running Tomcat behind a front-end web server. I have no specific advice beyond the usual, which is to start with something reproducible. Can you get the accept thread to die every time within a given time window after the server start? Does it happen with Tomcat standalone as well as behind a front-end server, or just the latter? Does it happen with the out-of-the-box server.xml or a heavily modified one? Yoav Shapira http://www.yoavshapira.com >-----Original Message----- >From: Keith Wannamaker [mailto:[EMAIL PROTECTED] >Sent: Friday, October 15, 2004 10:42 AM >To: [EMAIL PROTECTED] >Subject: 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: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
