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.

Bug 221957 - 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
Summary: o.a.lucene.store.LockReleaseFailedException: Cannot forcefully unlock a Nativ...
Status: RESOLVED INCOMPLETE
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.3
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 12:35 UTC by Tomas Danek
Modified: 2012-11-27 08:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2012-11-12 12:35:03 UTC 
Product Version: NetBeans IDE 7.3 Beta 2 (Build 201211062253)
Updates: NetBeans IDE is updated to version , NetBeans 7.3 Beta 2
Java: 1.6.0_26; Java HotSpot(TM) Client VM 20.1-b02
Runtime: Java(TM) SE Runtime Environment 1.6.0_26-b03
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
User directory: C:\Documents and Settings\tester\Application Data\NetBeans\7.3beta2
Cache directory: C:\Documents and Settings\tester\Local Settings\Application Data\NetBeans\Cache\7.3beta2
---------------------------------------
In repository browser, unable to browse local repo; Node is showing "no results - processing index message". Pushing "Update index" on Local node does not work.
Reason is probably this:
---------------------------------------
WARNING [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]: Indexing context could not be found: local
INFO [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]: Found a broken index at C:\Documents and Settings\tester\Local Settings\Application Data\NetBeans\Cache\7.3beta2\mavenindex\local with loaded contexts [central, hudson.snapshots, m.g.o-public, netbeans]
org.apache.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
	at org.apache.lucene.store.NativeFSLock.release(NativeFSLockFactory.java:295)
	at org.apache.lucene.index.IndexWriter.unlock(IndexWriter.java:4624)
	at org.apache.maven.index.context.DefaultIndexingContext.prepareCleanIndex(DefaultIndexingContext.java:231)
	at org.apache.maven.index.context.DefaultIndexingContext.prepareIndex(DefaultIndexingContext.java:205)
	at org.apache.maven.index.context.DefaultIndexingContext.<init>(DefaultIndexingContext.java:147)
	at org.apache.maven.index.context.DefaultIndexingContext.<init>(DefaultIndexingContext.java:155)
	at org.apache.maven.index.DefaultNexusIndexer.addIndexingContextForced(DefaultNexusIndexer.java:111)
[catch] at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.loadIndexingContext2(NexusRepositoryIndexerImpl.java:281)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.access$700(NexusRepositoryIndexerImpl.java:112)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$7.run(NexusRepositoryIndexerImpl.java:705)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$7.run(NexusRepositoryIndexerImpl.java:702)
	at org.openide.util.Mutex.writeAccess(Mutex.java:399)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.iterate(NexusRepositoryIndexerImpl.java:702)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.filterGroupIds(NexusRepositoryIndexerImpl.java:746)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.filterGroupIds(NexusRepositoryIndexerImpl.java:737)
	at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.getGroups(NexusRepositoryIndexerImpl.java:676)
	at org.netbeans.modules.maven.indexer.api.RepositoryQueries.getGroupsResult(RepositoryQueries.java:253)
	at org.netbeans.modules.maven.repository.GroupListChildren.createKeys(GroupListChildren.java:96)
	at org.openide.nodes.AsynchChildren.run(AsynchChildren.java:206)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1454)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2036)
---------------------------------------
We won't be able to track down why the lock was forgotten, but acceptable fix would be at least to delete such locks on IDE exit/start, since currently IDE restart does not help at all, and lock must be deleted manually :(
Comment 1 Tomas Danek 2012-11-12 12:41:58 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?
Comment 2 Milos Kleint 2012-11-12 12:43:08 UTC 
not sure.. I might have seen it before.. the new 5.0.0 version of the indexer if far from bug free..
Comment 3 Milos Kleint 2012-11-27 07:08:12 UTC 
(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?
Comment 4 Milos Kleint 2012-11-27 08:11:06 UTC 
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