The time window is within about 15 minutes. We run tomcat standalone,
with the standard http/11 connector. The server.xml is minimal. I
agree with the reproduceable angle, that is always a good place to start.
Keith
Shapira, Yoav wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
