Dear All, I have a problem when too few (only 2) Tomcat's threads is handling my requests. First a little background on what I'm trying to do: I have an web application, which loads a page. On loading the page there are Ajax script calls (DWR framework), requesting more data from the tomcat to be included into the calling page dynamically.
There can be as many as 100 separate requests (not usual but possible) per a page load via Ajax. Some of those requests can take a while because of waiting for another application, I'm trying to integrate with. Now the problem. I can see only 2 Tomcat Threads, handling all of these request, which as you can imagine can take a while. Shouldn't tomcat take a new Thread from the Thread Pool for each Request up to Maximum? Am I missing some configuration Tricks? Here is the thread pool configuration taken from the Manager.: Any Pointers/Suggestions/Tips would be greatly appreciated, Best Regards, Mirek Max threads: 150 Min spare threads: 25 Max spare threads: 75 Current thread count: 25 Current thread busy: 4 Max processing time: 226598 ms Processing time: 263.88 s Request count: 75 Error count: 14 Bytes received: 0.00 MB Bytes sent: 15.47 MB Stage Time B Sent B Recv Client VHost Request *S* 8775 ms 0 KB 0 KB 127.0.0.1 localhost POST /cmf/dwr/call/plaincall/FileDetailsDWRHelper.getFileChange.dwr HTTP/1.1 *S* 2146 ms 0 KB 0 KB 127.0.0.1 localhost GET /manager/status HTTP/1.1 *R* ? ? ? ? ? ? *R* ? ? ? ? ? ? *S* 245751 ms 0 KB 0 KB 127.0.0.1 localhost POST /cmf/dwr/call/plaincall/FileDetailsDWRHelper.getFileChange.dwr HTTP/1.1 *R* ? ? ? ? ? ? P: Parse and prepare request S: Service F: Finishing R: Ready K: Keepalive
