Hi Luis,
I agree with Jeanfrancois, it could be useful to get this testing
framework to investigate a stacktrace, when problem happens.
Meanwhile, case you pls. add following line, before starting
SelectorThread:
selectorThread.setMaxKeepAliveRequests(-1);
Theoretically it could fix the issue.
Thanks.
WBR,
Alexey.
On Jan 15, 2009, at 16:46 , Luis Neves wrote:
>
> I recently did an implementation of the WSTest[1] benchmark that
> uses Grizzly as the http engine. Not surprisingly this Java
> implementation leaves .NET in the dust :-) ... however one of the
> guys at MS involved with these kinds of benchmarks when trying to
> run the Grizzly based service on Windows2008 is having many
> stability problems.
> The entire discussion is here:
> <http://forums.microsoft.com/MSDNWorkShop/ShowPost.aspx?PostID=4274183&SiteID=64
> >
>
>
> Am I using Grizzly wrong?
> The code is here:
> <http://dl.getdropbox.com/u/279023/fast_wstest-1.2.tar.gz>
>
> Can anyone give any clues of what could be the problem?
>
> Thanks!
>
> --
> Luis Neves
>
> [1] - http://msdn.microsoft.com/wstest
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>