Bug 87059 - Can't launch eclipse on Mandrake 10 due to file locking issues.
Summary: Can't launch eclipse on Mandrake 10 due to file locking issues.
Status: RESOLVED DUPLICATE of bug 44735
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.0.1   Edit
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-03 06:37 EST by Paul Bristow CLA
Modified: 2005-03-03 10:02 EST (History)
0 users

See Also:


Attachments
Log file (9.46 KB, text/plain)
2005-03-03 06:38 EST, Paul Bristow CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Bristow CLA 2005-03-03 06:37:45 EST
I get an error when I try and launch eclipse.  The error in the log file is:

Caused by: java.io.IOException: An error occurred while locking file
"/ukrl/software/homes/bpb007/.eclipse/org.eclipse.platform_3.0.1/configuration/org.eclipse.core.runtime/.manager/.fileTableLock":
"No locks available". A probably reason is that the file system or Runtime
Environment does not support file locking. You may want to choose a different
location, or disable file locking (using the osgi.locking property), but this
can cause data corruption.

I've tried the following methods:

eclipse -vmargs -Dorg.eclipse.core.runtime.ignoreLockFile
eclipse osgi.locking=java.io
eclipse osgi.locking=none

I've no idea if I'm doing the right thing with the osgi.locking stuff.  I've
found bug reports saying I should use this method but no description of how to
do it.  Some reports mention a config.ini file but I don't have one in my
.eclipse directory.

I think there are several versions of this bug but I've trawled through most of
them and haven't found a solution.
Comment 1 Paul Bristow CLA 2005-03-03 06:38:50 EST
Created attachment 18430 [details]
Log file
Comment 2 Rafael Chaves CLA 2005-03-03 10:02:06 EST
You almost got it right:

eclipse -vmargs -Dosgi.locking=none

*** This bug has been marked as a duplicate of 44735 ***