users@glassfish.java.net

Re: App Server Complete Deadlock Occurs When HTTP Thread Limit Reached

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Tue, 03 Jul 2007 17:49:00 -0400

Hi,

glassfish_at_javadesktop.org wrote:
> On both the current 9.0 version and 9.1 beta when the HTTP Service Request Processing Thread Count (Maximum number of request processing threads) is reached NO OTHER deployed http servlet will respond and the App Server is deadlocked. The App Server must be shutdown (often requiring explicitly killing the process). The default Thread Count for 9.0 appears to be 5, and the 9.1 beta appears to be 20. Increasing these numbers does increase the number of concurrent web service calls before deadlock is reached, however this does appear to be a serious problem with the web servlet engine. I have created a trivial 100 line servlet which demonstrates this deadlock behavior which I can provide to anyone interested.

Yes I'm interested :-) Can you file an issue here:

https://glassfish.dev.java.net/servlets/ProjectIssues

and attach your test case? Assign it to me.

Thanks!

-- Jeanfrancois


> [Message sent by forum member 'steveshell' (steveshell)]
>
> http://forums.java.net/jive/thread.jspa?messageID=225117
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>