Originally posted by William Brogden:
I suspect that what happens is:
In case 1 the error in the requst Thread was caught and Tomcat managed to recover memory used by the request and was thus able to continue.
In case 2 Tomcat was not able to recover the memory.
The solution is generally proper programming technique that avoids "memory leaks" and algorithms that try to do too much in one request. Database operations that return a gazillion results for example.
In server.xml you can configure the number of connections that Tomcat will accept, etc.
Bill
Consider Paul's rocket mass heater. |