I also have had this problem, I increased the maxProcessors to 100, but still got the problem...
2004-02-22 17:55:49,230 ERROR [org.apache.tomcat.util.threads.ThreadPool] All threads are busy, waiting. Please increase maxThreads or check the servlet status100 100 YET, I know my load test program only has ten threads AND when I view the mbean for jbossweb in the jmx-console I can see max concurrent connects is 11 (1 for the console...) So my question on this is, where have the other 89 gone? David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, 7 February 2004 4:56 a.m. To: [EMAIL PROTECTED] Subject: [JBoss-user] [Installation & Configuration] - Re: All threads are busy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3820482#3820482 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3820482 Max depends how many concurrent threads your machine can handle and how many concurrent requests you expect to hit your web application. It's highly specific to your application, you can make some educated guesses but ultimately you need to load test on your production machine to find the ideal settings. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
