> Because it's already saturated with requests? No server has an infinite > capacity. How many threads did jstack report were running? > > Can you connect with JMX and see what state the connector is in? > > Are you using an Executor in combination with your Connector?
Thanks for your quick reply. we didn't use Executor, and there is no JMX with tomcat. When beginning of error occurs, there is more than 600 worker threads(most of them is waiting), an hour later, there's only 50 worker threads left(I think because of idle, threads were killed by pool), BUT tomcat still can't process requests, nginx still report connection timeout for most request, I can't understand why this happened? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
