Hi Alan,
it looks like some file handle leak either in Grizzly or your custom
code.
It could be very useful to see your code, if it's possible. If you can
propose the testcase, which reproduces your issue - it could be even
better :)
Thanks.
WBR,
Alexey.
On Aug 26, 2008, at 13:57 , Alan Williamson wrote:
> Guys,
>
> We are having major problems keeping Grizzly up under heavy load.
> Its just not hacking it. I've reported this problem before, but it
> wasn't resolved.
>
> What happens is that Grizzly simply stops accepting requests on
> Port#80.
>
> It won't do a thing more when it receives the error @
>
> http://clients.aw20.net/whiteboard/?b=92181#610
>
> The stack trace of the Java program yeilds the following:
>
> http://clients.aw20.net/whiteboard/?b=92181
>
> As you can see, its all stuck in Grizzly threads, with the engine
> doing absolutely nothing!!!! Grizzly has just given up.
>
> This is the latest 1.8.5.3 JAR files for Grizzly, and we are simply
> using the framework and http-webserver JAR files.
>
> Running on JDK1.6 / Redhat
>
> Please advise. This is a major show stopper.
>
> --
> Alan Williamson
> Registrationless email/sms reminders: http://yourli.st/
> blog: http://alan.blog-city.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>