Hi,
you are using the Coyote Connector, right? Grizzly doesn't have such
limitations as it use nio non blocking under the hood, which solves the
one connection per thread problem of "blocking" Web Server.
To increase the number of threads, use the request-processing attribute
called thread-count under http-service instead of the acceptor-threads.
Thanks
-- Jeanfrancois
glassfish_at_javadesktop.org wrote:
> Hi,
>
> I'm running a loadtest on an application running on glassfish v2 final release b58g x86. After a few minutes I get this error message in the server.log of the glassfish.
> [#|2007-10-09T20:21:26.585+0200|SEVERE|sun-appserver9.1|org.apache.tomcat.util.threads.ThreadPool|_ThreadID=18;_ThreadName=TP-Processor4;_RequestID=bc3c9ab2-
> de43-4240-b545-10604dfe19ae;|PWC5750: All threads (200) are currently busy, waiting. Increase http-listener attribute acceptor-threads (200) or check the servlet status|#]
>
> I increased the thread-pool from 200 to 400 without changing this message. Where do I configure these acceptor-threads?
>
> By creating a thread dump I see less than 10 threads running our application and there is nothing else deployed. the same I can see when i activate monitoring in web console.
>
> How can I find out what's the brake in this app-server?
> There are 4 databases configured and used by the application. Each is configured with 200 connections.
>
> Thanks,
> Uwe
> [Message sent by forum member 'bartels' (bartels)]
>
> http://forums.java.net/jive/thread.jspa?messageID=239176
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>