Huy This RequestProcessor enqueues requests and services on as needed basis....you can easily substitute jdbc connections for corba connections http://www.koders.com/java/fid327B70539EF40AE0E75381B058FB06D9B1BFFE61.aspx
M- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents ----- Original Message ----- From: "Huy Vo (hvo)" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Friday, November 03, 2006 3:27 PM Subject: Thread pool per webapp? Hi, I am wondering whether Tomcat supports thread pool configuration for each webapp. My understanding is that all webapps share the pool configured for the connector. Let's say I have webapps A and B, and A is more critical webapp. Let's say my connector's pool size is 100, and there are 100 concurrent requests destined for A and B each (so total 200 requests here). I would like to allocate 70 threads to process A's requests, and only 30 for B's. Is this something that Tomcat supports? If not, what would be a good alternative strategy for it? I am thinking of using a RequestProcessor to reject requests depending on its destination but that is not very elegant as requests are rejected instead of being queued. Thanks in advance. Regards. =================== Huy T. Vo Voice: 408-853-0535 Fax: 408-853-4021
