This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | o.a.lucene.store.LockReleaseFailedException: Cannot forcefully unlock a NativeFSLock which is held by another indexer component: C:\Documents and Settings\tester\Local Settings\Application Data\NetBeans\Cache\7.3beta2\mavenindex\local\write.lock | ||
---|---|---|---|
Product: | projects | Reporter: | Tomas Danek <musilt2> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Tomas Danek
2012-11-12 12:35:03 UTC
hmm, may be a really obscure scenario - in taskmgr was hanging some netbeans.exe process, which was apparently holding lock. May not be worth to bother with this at all -> WONTFIX? not sure.. I might have seen it before.. the new 5.0.0 version of the indexer if far from bug free.. (In reply to comment #1) > hmm, may be a really obscure scenario - in taskmgr was hanging some > netbeans.exe process, which was apparently holding lock. > May not be worth to bother with this at all -> WONTFIX? well, technically one should not be allowed to have 1 cache directory for multiple running instance of netbeans, right? when I kill the process (not application) I do get a writable.lock file remaining in the index directory. However upon restart, I cannot observe any problems, index gets reloaded, no exception logged. closing as incomplete (the problem apparently occurred but we have no idea how to reproduce) without steps to reproduce it's hard to fix such things. BTW. I've tested with indexer 5.1.0, the bug was reported against 5.0.0 |