Salut,
glassfish_at_javadesktop.org wrote:
> Hi
>
> We have a problem with Glassfish-2.1.
> Everything is running well several days but sometimes GF stops responding.
> I've monitored GF while down time all 5 request processing threads were busy and
> open connections count was increasing. I couldn't see any problem in thread dump.
> Colud you please help, what is locking request processing threads ?
Can you send the thread dump when it starts queing requests? I suspect
the WorkerThread are locked on the db connection pool/ jdbc. When that
happens, Grizzly starts queuing requests until it reach the max (4096)
then start dropping request (this is to prevent DoS). Increasing the
thread might help but would be better to see what happening when it
start slowing down.
A+
-- jeanfrancois
>
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
>
> Centos 5.2 on 64bit Intel Xeon 2 x quad core.
> [Message sent by forum member 'osmanizbat' (osmanizbat)]
>
> http://forums.java.net/jive/thread.jspa?messageID=337924
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>