lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <bimargul...@gmail.com>
Subject Re: Hanging with fixed thread pool in the IndexSearcher multithread code
Date Sun, 19 Feb 2012 16:52:50 GMT
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 <rcmuir@gmail.com> wrote:

> On Sun, Feb 19, 2012 at 9:08 AM, Benson Margulies <bimargulies@gmail.com> 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 executor service at all.
>>
>> Is this expected? Should the javadoc say something? (I can make a patch).
>>
>
> I'm not sure I understand the details here, but I don't like the sound
> of 'different results': is it possible you can work this down into a
> test case that can be attached to jira?
>
>
> --
> lucidimagination.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message