Hello Allan,
according to the JStack thread dump - most of the Grizzly worker
threads are free and ready to execute the requests.
By "server died" you mean, that it stops to accept requests? Does the
telnet work on the port?
Pls. let me know... Depending on the answer we will try to localize
the issue.
Thank you.
WBR,
Alexey.
On Sep 2, 2008, at 13:03 , Alan Williamson wrote:
> Jeanfrancois, here is the output of the SNAPSHOT jar file you gave
> me, including the netstat -an output.
>
> http://clients.aw20.net/whiteboard/?b=36267
>
> JStack thread dump:
>
> http://clients.aw20.net/whiteboard/?b=72819
>
>
> It dies very quickly, within minutes. Its not getting a huge amount
> of traffic YET, it is merely processing 1x1.gif of 49bytes each!
> So lots of small requests.
>
>
>
> Alan Williamson wrote:
>> This morning we moved one of the Grizzly servers out from behind
>> nginx into its own world, and it died on its ass very quickly.
>> A quick look around and we see we've run up against this:
>> http://forums.java.net/jive/thread.jspa?messageID=273693
>> Which i see is still left unresolved. This was reported in the
>> Glassfish forums but applies to us as well.
>> So it would appear that nginx is managing the network connections
>> infinitely better than Grizzly is on its own, because as soon as we
>> put it back behind nginx, all is well again.
>> I don't want to have to put nginx in this path
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>