On Jakarta Tomcat's weakness

I've done a lot of work with Jakarta Tomcat. My Tomcat setup handled 30000 online users. Tuning the JVM for that was a nightmare but it pretty much worked.

But there remains one problem with Tomcat. A problem which I've reported a number of times to the developers but with no result. Once Tomcat is hit with tons of requests, and all the worker threads are depleted, it fails and never recoils. So basically instead of waiting for one of the threads to finish it's work and passing the next request to it, Tomcat simply does nothing.

I wonder if this will ever get fixed. And until it doesn't - I don't recommend using Tomcat for any production setup.