[
https://issues.apache.org/jira/browse/LUCENENET-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-189:
---------------------------
Attachment: TestIndexWriter.patch
OK I found the bug. docWriter being null is an expected behaviour. In
TestIndexWriter , It should be checked with NullReferenceException instead of
ArgumentNullException.
DIGY
> Occasional failures in TestIndexWriter/TestAddIndexesWithCloseNoWait
> --------------------------------------------------------------------
>
> Key: LUCENENET-189
> URL: https://issues.apache.org/jira/browse/LUCENENET-189
> Project: Lucene.Net
> Issue Type: Bug
> Environment: v2.4.0
> Reporter: Digy
> Attachments: IndexWriter ShowBug.patch, TestIndexWriter.patch
>
>
> {code}
> finally
> {
> docWriter.ResumeAllThreads(); //<--- docWriter is null
> }
> {code}
> Object reference not set to an instance of an object.
> at Lucene.Net.Index.IndexWriter.AddIndexes(Directory[] dirs) in
> .......\src\Lucene.Net\Index\IndexWriter.cs:line 3033
> at Lucene.Net.Index.TestIndexWriter.CommitAndAddIndexes3.DoBody(Int32 j,
> Directory[] dirs)
> at Lucene.Net.Index.TestIndexWriter.AddIndexesThread.Run()
> DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
