Remy Maucherat wrote: >>I tried this (not in a live-situation, but with ab), but I don't see any >>difference. I can't reproduce the situation with ab. But it's still >>happening in the live-server. Could it be 150 processors isn't enough in >>our situation? >> > > Maybe. It depends on the number of simultaneous users accessing the server. > If you go beyond what a single standalone Tomcat can provide (which is > constrained by your OS, usually), you have to set up some load balancing > (using JK and TC 4.0.2). >
I know. At the moment we added a lot of oscache-tags to our jsp-pages and increased the maxProcessors to 255. Untill now we didn't ran out of processors. 150 Processors for 300000 request/day were probably not enough. > By your comments, I understand that you also get the "out of processors" > problem with the HTTP/1.0 connector. Is that right ? > Not exactly. I did some testing using ab, and both the HTTP/1.0 and HTTP/1.1 connector ran out of processors, but it was when using a maxProcessors of 150 and more than 150 simultaneous requests. And when ab finished the server was still running. So this is normal behaviour. I couldn't reproduce the situation where I got the "out off processors" message and the server allmost crashed as it did in the live situation. Gerard -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
