[
https://issues.apache.org/jira/browse/LUCENE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877482#comment-13877482
]
Mikhail Khludnev commented on LUCENE-5407:
------------------------------------------
I don't think so.
Why do you recreates indexwriter in this test, even if you have a reason, it's
definitely not the case for which it was designed.
Also, I see that ParsingReader.run() calls indexWriter.addDocument(doc); when
indexWriter might be already closed in the main thread.
Anyway, please post thread dump with the deadlock that clarifies a lot.
> Deadlock? while indexing reader fields in cascaded threads
> ----------------------------------------------------------
>
> Key: LUCENE-5407
> URL: https://issues.apache.org/jira/browse/LUCENE-5407
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Affects Versions: 4.6
> Environment: Windows 7 64 bits, JRE 1.7.0_25 64 bits
> Reporter: Luis Filipe Nassif
> Attachments: Test.java
>
>
> Apparently I found a deadlock problem with IndexWriter using Reader Fields in
> a cascaded thread design to add documents (I am working on an application
> integrating Tika, which has the capability to add embedded documents to the
> index as independent documents as they are found). The attached code
> illustrates the problem. Sometimes it stops processing, at least one of the
> threads remains in WAITING state. It must be executed no more than 5 times in
> my environment to trigger the problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
