Re: [jetty-discuss] About BoundedThreadPool.dispatch implementation

[Jesse M. <jes...@gm...>]

two things

1) this list is not being used anymore, use the
us...@je...(this is cc'd there)

2) BoundedThreadPool has been deprecated in favor of QueuedThreadPool so
give that a whirl :)

cheers!
jesse

On Wed, Oct 29, 2008 at 8:28 AM, Aleksi Kallio <ale...@cs...> wrote:

> Hi,
>
> > Of course testing will reveal if updating from 6.1.1 to 6.1.12 will
> > resolve the issue, but as it is quite laborous to reproduce and not very
> > repeatable, it would be nice to know a bit more about what has happened
> > at the code level.
>
> We did now some testing. We have one Jetty instance, serving HTTP and
> acting as a file broker in our system. It is an embedded Jetty with
> default settings.
>
> When we hit 6.1.1 it with requests from 10 machines we get "dispatch
> failed", and the socket closes. After updating to 6.1.11 there is no
> "dispatch failed", but unfortunately Jetty is stuck anyway.
>
> I will keep reading the BoundedThreadPool source code and try to figure
> out what is wrong. Also we will redo the testing with debug logging
> enabled.
>
> All suggestions are of course warmly welcome. :)
>
> Cheers,
> Aleksi
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> jetty-discuss mailing list
> jet...@li...
> https://lists.sourceforge.net/lists/listinfo/jetty-discuss
>



-- 
jesse mcconnell
jes...@gm...