Restarting the HTTP listener creates new threads which is why it starts
working again. You need to figure out why the threads are locking in
the first place. When it locks up, please run this command:
asadmin generate-jvm-report --type=thread > thread_dump.txt
Send it to this mailing list. Someone from Sun will be able to help you
determine why the threads are blocked. As in my case, you will probably
find that Grizzly is not the cause. Grizzly was waiting on resource
manager to give me a database connection, and resource manager was
waiting on JDBC driver to log in. JDBC driver was waiting forever
because it had no timeout set. In this scenario, coyote will just
give you an HTTP error instead of waiting for one of the blocked threads
to become available.
Ryan
glassfish_at_javadesktop.org wrote:
> Hi,
>
> I've been following this issue as I've come across this problem as well. My details are:
>
> - Sun Java System Application Server 9.0 update 1(so older than the one Kevin is using)
>
> - Redhat Linux 5
>
> I am running web services on my HTTPS port and after a while (it changes depending upon the load of course), usually a day or so, the calls to the HTTPS port just stop working. No exception, nothing. Calls to the HTTP port and the Admin port work fine.
>
> So I first tried enabling/disabling some property on the http listener for the HTTPS port and sure enough it started working again right away.
>
> Next I am going to try switching from Grizzly to Coyote as talked about here. I will post result after running with that for a while.
> [Message sent by forum member 'bkatnich' (bkatnich)]
>
> http://forums.java.net/jive/thread.jspa?messageID=275069
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>