lucboudreau at gmail.com
Mon Aug 15 12:29:55 EDT 2011
To be exact, yes I do use the same thread pool for both the shepherd thread
and the execution threads, but the class initialization routine launches a
single static FutureTask which performs the shepherding, and this task is
not killed until the JVM shuts down. The requests coming in later on create
new threads from that same pool and are re-used as necessary. As before,
each request can be processed concurrently.
On Mon, Aug 15, 2011 at 12:21 PM, Joe Barnett <thejoe at gmail.com> wrote:
> Hi Luc,
> One comment:
> On Mon, Aug 15, 2011 at 9:03 AM, Luc Boudreau <lucboudreau at gmail.com>
> > Hi Julian,
> > I used a dedicated daemon thread so that one and only one thread would
> > this process...
> It looks like you're rather using a dedicated thread pool, not a
> single thread? Executors.newCachedThreadPool() should be creating new
> threads as necessary, I believe. Which should be what we want anyway,
> so that concurrent query requests are not serialized behind one
> another. Haven't gotten around to testing this yet though, have you?
> Mondrian mailing list
> Mondrian at pentaho.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian