[
https://issues.apache.org/jira/browse/LUCENE-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated LUCENE-3803:
-------------------------------------
Description:
The test case I'm about to attach creates an executor service uses invokeAll to
run things from it. The 'things' (Callable) that it runs in turn run Lucene
searchers using a searcher that has the very same executor service. This turns
out to hit some sort of deadlock related to the executor service queue.
I won't be terribly surprised if this is really a matter of a fundamental
limitation of the executor service, but if nothing else this JIRA might provoke
a warning in the javadoc. Or, what do I know, maybe there's a way Lucene could
interact with the executor service that gets along with this?
was:
The test case I'm about to attach creates an executor service uses invokeAll to
run things from it. The 'things' (Callable) that it runs in turn run Lucene
searchers using a searcher that has the very same executor service. This turns
out to hit some sort of deadlock related to the executor service queue.
I won't be terribly surprised if this is really a matter of a fundamental
limitation of the executor service, but if nothing else this JIRA might provoke
a warning in the javadoc. Or, what do I know, maybe there's a way Lucene could
interact with the executor service that gets along with this?
> Using a searcher with an executor service does not work from within a
> Callable called by that same executor service
> -------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3803
> URL: https://issues.apache.org/jira/browse/LUCENE-3803
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/search
> Affects Versions: 3.5
> Reporter: Benson Margulies
> Attachments: lucene-tc.tgz
>
>
> The test case I'm about to attach creates an executor service uses invokeAll
> to run things from it. The 'things' (Callable) that it runs in turn run
> Lucene searchers using a searcher that has the very same executor service.
> This turns out to hit some sort of deadlock related to the executor service
> queue.
> I won't be terribly surprised if this is really a matter of a fundamental
> limitation of the executor service, but if nothing else this JIRA might
> provoke a warning in the javadoc. Or, what do I know, maybe there's a way
> Lucene could interact with the executor service that gets along with this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
