https://bz.apache.org/bugzilla/show_bug.cgi?id=65455
--- Comment #4 from Mark Thomas <ma...@apache.org> --- The thread dump you provided shows that Tomcat is blocking new connections because the maxConnections limit has been reached. This means that Tomcat isn't tracking completed connections correctly but finding out where this is going wrong is non-trivial. If the average number of concurrent requests is low, you should be able to reduce maxConnections significantly. If reaching the maxConnections limit is the problem, the problem should trigger a lot faster than ~10 days with a lower limit. I'd suggest setting to to 100. It should trigger in a few hours. Confirming that the issue is related to reaching maxConnections is the first step towards a fix. Please answer the following questions: 1. What is the impact of reducing maxConnections to 100? 2. What is the impact of switching from NIO2 to NIO (with maxConnections="100") ? 3. What is the impact of using NIO2 with maxConnections="-1" ? 4. What is the nature of the web application where this is observed? Does is use the Servlet async API? Does it use the Servlet non-blocking API? Does it use WebSocket? 5. Does this issue still occur with NIO2, maxConnections="100" and the latest 8.5.x release? By all means provide us with additional information you think might be helpful but if you don't also provide answers to the questions we ask, we are unlikely to be able to help. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
