On Sun, Feb 19, 2012 at 8:07 PM, Uwe Schindler <[email protected]> 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 other. > > Use a separate thread pool for Lucene (or whenever you execute new callables > from within another running callable)
Right. There's nothing like coding a test case to cast one's stupid errors into high relief. Sorry for all the noise. > > Uwe > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: [email protected] > >> -----Original Message----- >> From: Benson Margulies [mailto:[email protected]] >> Sent: Monday, February 20, 2012 1:47 AM >> To: [email protected] >> 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 protect >> the >> next person from making the same mistake. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
