Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-20 Thread Benson Margulies
On Sun, Feb 19, 2012 at 10:39 PM, Trejkaz wrote: > On Mon, Feb 20, 2012 at 12:07 PM, Uwe Schindler wrote: >> See my response. The problem is not in Lucene; its in general a problem of >> fixed >> thread pools that execute other callables from within a callable running at >> the >> moment in the

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Trejkaz
On Mon, Feb 20, 2012 at 12:07 PM, Uwe Schindler wrote: > See my response. The problem is not in Lucene; its in general a problem of > fixed > thread pools that execute other callables from within a callable running at > the > moment in the same thread pool. Callables are simply waiting for each

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Benson Margulies
t; > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > >> -Original Message- >> From: Benson Margulies [mailto:bimargul...@gmail.com] >> Sent: Monday, February 20, 2012 1:47 AM >> To:

RE: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Uwe Schindler
2 1:47 AM > To: java-user@lucene.apache.org > Subject: Re: Hanging with fixed thread pool in the IndexSearcher multithread > code > > See https://issues.apache.org/jira/browse/LUCENE-3803 for an example of the > hang. I think this nets out to pilot error, but maybe Javadoc could p

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Benson Margulies
See https://issues.apache.org/jira/browse/LUCENE-3803 for an example of the hang. I think this nets out to pilot error, but maybe Javadoc could protect the next person from making the same mistake. - To unsubscribe, e-mail: java-u

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Benson Margulies
Conveniently, all the 'wrong-result' problems disappeared when I followed your advice about counting hits. On Sun, Feb 19, 2012 at 10:39 AM, Robert Muir wrote: > On Sun, Feb 19, 2012 at 9:08 AM, Benson Margulies > wrote: >> 3.5.0:  I passed a fixed size executor service with one thread, and >>

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Benson Margulies
and there was a dumb typo. 1 thread: hang 2 threads: hang 3 or more: no hang On Feb 19, 2012, at 10:40 AM, Robert Muir wrote: > On Sun, Feb 19, 2012 at 9:08 AM, Benson Margulies > wrote: >> 3.5.0: I passed a fixed size executor service with one thread, and >> then with two threads, to the In

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Benson Margulies
I should have been clearer; the hang I can make into a test case but I wondered if is would just get closed as 'works as designed'. the result discrepancy needs some investigation, I should not have mentioned it yet. On Feb 19, 2012, at 10:40 AM, Robert Muir wrote: > On Sun, Feb 19, 2012 at 9:08

Re: Hanging with fixed thread pool in the IndexSearcher multithread code

2012-02-19 Thread Robert Muir
On Sun, Feb 19, 2012 at 9:08 AM, Benson Margulies wrote: > 3.5.0:  I passed a fixed size executor service with one thread, and > then with two threads, to the IndexSearcher constructor. > > It hung. > > With three threads, it didn't work, but I got different results than > when I don't pass in an