Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347702

Summary:	[Help][Search] IndexingException on Solaris-GTK
Product:	[Eclipse Project] Platform	Reporter:	Grant Gayed <grant_gayed>
Component:	User Assistance	Assignee:	platform-ua-inbox <platform-ua-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	cgold, Mike_Wilson, mober.at+eclipse
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Solaris-GTK
Whiteboard:	stalebug

Description Grant Gayed

2011-05-30 16:47:37 EDT

- 3.7RC3 build
- observed on Solaris-GTK

- I'm not sure which view caused this exception, as it happened while I was opening all of them simultaneously (Window > Show View > Other...), but presumably you would know which view could cause this
- After opening all of Eclipse's views the following was written to my error log.  It appears to be failing to get an NSF lock.  I think this has come up in the past, but a fix was made to handle it, so I'm not sure if this is the same case.

!ENTRY org.eclipse.help.base 4 0 2011-05-30 16:26:25.859
!MESSAGE Unable to Lock Help Search Index
!STACK 0
java.io.IOException: Invalid argument
	at sun.nio.ch.FileChannelImpl.lock0(Native Method)
	at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:882)
	at java.nio.channels.FileChannel.tryLock(FileChannel.java:962)
	at org.eclipse.help.internal.search.SearchIndex.tryLock(SearchIndex.java:956)
	at org.eclipse.help.internal.search.SearchIndex.<init>(SearchIndex.java:172)
	at org.eclipse.help.internal.search.SearchIndex.<init>(SearchIndex.java:142)
	at org.eclipse.help.internal.search.SearchIndexWithIndexingProgress.<init>(SearchIndexWithIndexingProgress.java:24)
	at org.eclipse.help.internal.search.LocalSearchManager.getIndex(LocalSearchManager.java:186)
	at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:25)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

!ENTRY org.eclipse.help.base 4 0 2011-05-30 16:26:29.212
!MESSAGE Exception occurred in search indexing at beginAddBatch.
!STACK 0
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/bluebird/teamswt/ggayed/37RC3/solaris-x86/eclipse/configuration/org.eclipse.help.base/index/en_US/write.lock: java.io.IOException: Invalid argument
	at org.apache.lucene.store.Lock.obtain(Lock.java:85)
	at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:1545)
	at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1074)
	at org.eclipse.help.internal.search.SearchIndex.beginAddBatch(SearchIndex.java:280)
	at org.eclipse.help.internal.search.IndexingOperation.mergeIndexes(IndexingOperation.java:548)
	at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:152)
	at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
	at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:670)
	at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:644)
	at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:31)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.io.IOException: Invalid argument
	at sun.nio.ch.FileChannelImpl.lock0(Native Method)
	at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:882)
	at java.nio.channels.FileChannel.tryLock(FileChannel.java:962)
	at org.apache.lucene.store.NativeFSLock.obtain(NativeFSLockFactory.java:233)
	at org.apache.lucene.store.Lock.obtain(Lock.java:99)
	... 10 more

!ENTRY org.eclipse.help.base 4 0 2011-05-30 16:26:29.214
!MESSAGE Error indexing documents
!STACK 0
org.eclipse.help.internal.search.IndexingOperation$IndexingException
	at org.eclipse.help.internal.search.IndexingOperation.mergeIndexes(IndexingOperation.java:549)
	at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:152)
	at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
	at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:670)
	at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:644)
	at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:31)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Chris Goldthorpe

2011-05-31 10:46:37 EDT

The one bug that sounds similar was reported on HP/UX - Bug 236046. Was the drive NFS mounted in this case?

Comment 2 Chris Goldthorpe

2011-05-31 23:44:35 EDT

Copying Martin Oberhuber. This problem seems to be related to Eclipse being installed on an NFS mounted disk - Martin, as a consumer of Eclipse on Solaris have you seen this problem before?

Comment 3 Chris Goldthorpe

2011-06-01 15:45:47 EDT

This may be related to Bug 44735 .

Comment 4 Chris Goldthorpe

2011-06-01 18:35:28 EDT

I have just installed Eclipse 3.7RC3 on a virtual machine running Solaris 11 Express. I opened Eclipse and performed a Help/Search, this built the search index correctly and there were no problems reported in the error log view.

I repeated the experiment with Eclipse installed on an NFS drive which belonged to another machine and was mounted locally. Again the search index was built correctly and the error log was clean.

Finally after deleting the search index I tested with the Eclipse installation and the workspace both on an NFS drive. Once again the search index built correctly and the error log was clean.

I think there is still a problem but it takes specific and possibly unusual circumstances to recreate it. This bug should be deferred until after 3.7.

Comment 5 Lars Vogel

2019-11-14 02:19:00 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.