| Summary: | Eclipse 3.0 file locking exception on startup | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Grant Martin <grantmartin> |
| Component: | Current packages | Assignee: | Karl Trygve Kalleberg (RETIRED) <karltk> |
| Status: | VERIFIED NEEDINFO | ||
| Severity: | normal | CC: | gentoo |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://www.javageek.org/archives/001102.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Grant Martin
2004-07-20 04:46:42 UTC
The line: # eclipse -vmargs -Dosgi.locking=none Is meant to be: # eclipse-3 -vmargs -Dosgi.locking=none And I forgot to mention i'm using reiserfs I have tried to compile with FEATURES="-sandbox" and still have the same problem Are you running some strange kernel or some strange file system? Exactly which kernel and which file system do you run this on? Is /home/gm99 on a network file system? If so, which? Can this be reproduced with a different VM, suck as the dev-java/jrockit-jdk-bin? Yes my home directory is on a network filesystem (NFS v3). Is this a problem? My Kernel is 2.6.6 gentoo development sources and the rest of my system is on a reiserfs file system I will try that different VM when I get a chance, but have already tried both blackdown and sun vm. Unless you also have grsecurity enabled, which sometimes create strange
problems, I think this problem is related to NFS.
If it is, I cannot do much to help you, since we don't have the source code
for the blackdown JVM:/
Please try a different JVM, and if that still fails, attempt this hack:
let ${HOME}/.eclipse be a symlink to /tmp/gm99/.eclipse (hopefully tmp is a local filesystem, or there wouldn't be much point to this).
If that works, I think we've pretty much nailed NFS as being the culprit.
I know file locking over NFS has been problematic for years, but I honestly
thought it was a (mostly) solved problem.
I suspect there is something weird with your NFS setup. Are you running lockd? Turns out that upgrading from sun jdk 1.4.2_02 to sun jdk 1.4.2_04 fixed the problem. Didn't realise 1.4.2_03 was the minimum requirement. Thanks for your help anyway. i have the same problem. my home dir is on the local harddrive. using sun-j2sdk-1.4.2. eclipse starts with the osgi.locking=none parameter |
