lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENENET-135) Race condition in DocumentsWriter.UpdateDocument
Date Sat, 19 Jul 2008 20:47:31 GMT

     [ https://issues.apache.org/jira/browse/LUCENENET-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Digy updated LUCENENET-135:
---------------------------

    Attachment: DocumentsWriter+SupportClass.rar

Since calling Monitor.PulseAll or Monitor.Wait before Monitor.Enter results in SynchronizationLockException
(which is the case in code after removing "lock(this)"es ) I chose AutoResetEvent that is
most suitable for wait/notify.

I also coded a new class "SyncObject" for java's synchronized methods that allows nested locks
of the same object in the same thread just like 
{code}
lock(this) 
{
   .....
   lock(this)
   {
      .....
   }
}
{code}

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
>
>
> 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.


Mime
View raw message