> It looks quite strange. Does Apache still dispatch
> properly request to
> GlassFish?
Quite strange indeed. From my tests I can confirm that Apache does dispatch requests to Glassfish (by sniffing the network traffic) but Glassfish never replies to them and I get the following message in the log:
PWC5750: All threads (200) are currently busy, waiting. Increase http-listener attribute acceptor-threads (200) or check the servlet status
If I restart the domain everything works fine for about two weeks and this happens again. I can see that the number of TP-Processor threads slowly increases over time till it reaches 200 and then the server stops responding. The server is very light loaded, so there is no way 200 threads would be needed in normal operation. It seems that the threads are getting "stuck" and Glassfish is creating new ones to service new requests till it reaches the 200 limit.
Any hints on how can I troubleshoot/solve this?
P.S.: Sorry for the delay, my e-mail was incorrect on my profile and I wasn't notified that you replied to this thread.
>
> Thanks
>
> -- Jeanfrancois
>
>
>
> >
> > Any hints?
> > [Message sent by forum member 'lbschenkel'
> (lbschenkel)]
> >
> >
> http://forums.java.net/jive/thread.jspa?messageID=2821
> 67
> >
> >
> ------------------------------------------------------
> ---------------
> > To unsubscribe, e-mail:
> users-unsubscribe_at_glassfish.dev.java.net
> > For additional commands, e-mail:
> users-help_at_glassfish.dev.java.net
> >
>
> ------------------------------------------------------
> ---------------
> To unsubscribe, e-mail:
> users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail:
> users-help_at_glassfish.dev.java.net
[Message sent by forum member 'lbschenkel' (lbschenkel)]
http://forums.java.net/jive/thread.jspa?messageID=285308