Hi,
>
> If I've been following closely enough, I believe that grizzly 1.9.1
> is using a leader/follower strategy for the thread pool (and when I
> look at stack dumps, that seems to be what is happening too...)
>
> Is that configurable in any way (and configurable through
> glassfish)? When I run certain tests that make a lot of connections,
> I get some starvation of accept calls; it seems like no one becomes
> the leader if there is too much other work? The end result is that
> some new connections to the server time out.
>
> This is on fairly big hardware, and I would typically have 4
> acceptor threads in previous versions. Is there some other way I can
> get more resources into an accept call?
This is correct, when using Leader/follower strategy, selector threads
are actually executed in worker thread pool. So, finally this could
really get to starvation of accept or read calls, if all workers are
getting busy with request processing.
WBR,
Alexey.
>
>
> -Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>