[
https://issues.apache.org/jira/browse/LUCENENET-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-135:
---------------------------
Attachment: DocumentsWriter.patch
I will attach a new DocumentsWriter.patch, which was applied to lucene.java at
March, 3rd 2008 with a comment
"LUCENE-1198: don't increment numDocsInRAM unless
DocumentsWriter.ThreadState.init succeeds".
(after the release of 2.3.1).
It is not directly releated with this issue but can be used.
DIGY.
> Race condition in DocumentsWriter.UpdateDocument
> ------------------------------------------------
>
> Key: LUCENENET-135
> URL: https://issues.apache.org/jira/browse/LUCENENET-135
> Project: Lucene.Net
> Issue Type: Bug
> Environment: 2.3.1
> Reporter: Digy
> Attachments: DocumentsWriter+SupportClass.rar,
> DocumentsWriter-Temp.patch, DocumentsWriter.patch, DocumentsWriter.patch,
> SupportClass.patch
>
>
> There is a race condition in DocumentsWriter.UpdateDocument. Locking the
> whole method solves the problem but this is not what is intended in java
> version
> (testcase: Index/TestIndexWriter/TestDocumentsWriterExceptionThreads)
> I am working on it.
> DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
