lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <j...@apache.org>
Subject [jira] Closed: (LUCENENET-112) orphan IndexWriter locks
Date Wed, 19 Nov 2008 22:27:44 GMT

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

Digy closed LUCENENET-112.
--------------------------

    Resolution: Won't Fix
      Assignee: Digy

The target of this issue was Lucene.Net 2.1.  I can't regenerate it with 2.3.1. 

DIGY.

> orphan IndexWriter locks
> ------------------------
>
>                 Key: LUCENENET-112
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-112
>             Project: Lucene.Net
>          Issue Type: Bug
>            Reporter: Digy
>            Assignee: Digy
>         Attachments: SimpleFSLockFactory.patch, TestLockFactory.patch
>
>
> If an application crashes while an IndexWriter is open, it leaves the lock file(writer.lock)
behind. Re-running the application results in an "Lock obtain timeout" exception.

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