Hello,
I am getting similar problem, and i still have not been able to find
out why. it seems that increasing the number of worker threads, and
decreasing the thread timeout, makes the problem appear less, but not
completely go away.
currently, once the thread pool is full, my glassfish hangs for a
certain amount of time, then continues to work. it is a small glitch.
are you using postgresql?
Best.
-C.B.
On Fri, Jan 22, 2010 at 5:50 AM, <glassfish_at_javadesktop.org> wrote:
> I came across this old thread at http://old.nabble.com/Server-stops-responding-due-to-Glassfish-td16964918i60.html.
>
> We've been getting similar symptoms on our Glassfish server but have never been able to determine why it just suddenly hangs up forcing a full server restart. I generated the jvm report as described in the old thread and am still waiting for the server to hang up again so I'd like to know what kind of flags should I be looking out for in the next report.
>
> I presume that "No deadlock found" at the end of the report is expected since the server is still working, but other than the absence of "No deadlock found", what else should I be looking out for?
> [Message sent by forum member 'oilagan' (oilagan_at_systemacorp.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=382289
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>