Bug 50612 - Eclipse won't start
Summary: Eclipse won't start
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-26 10:48 EST by Marcus Schlueter CLA
Modified: 2004-01-30 17:14 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Schlueter CLA 2004-01-26 10:48:16 EST
Hello,
i have the sun jdk1.4.2 installed on my gentoo box. i also have the Eclipse
3.0M5 installed but they won't start.

The following output will generated in the log:

!ENTRY org.eclipse.core.launcher 4 0 Jan 26, 2004 08:20:20.32
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at
org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBootLoader.java:1049)
        at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:838)
        at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:299)
        at org.eclipse.core.launcher.Main.run(Main.java:767)
        at org.eclipse.core.launcher.Main.main(Main.java:601)
Caused by: org.eclipse.core.runtime.CoreException: Unable to create platform
lock file: /home/ally/.eclipse/workspace/.metadata/.lock.
        at
org.eclipse.core.internal.runtime.InternalPlatform.createLockFile(InternalPlatform.java:228)
        at
org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(InternalPlatform.java:641)
        ... 14 more
Comment 1 Rafael Chaves CLA 2004-01-26 10:57:45 EST
Please see bug 44735 for problem description and workaround. 

If your workspace is not mounted on a NFS file system, please reopen.

*** This bug has been marked as a duplicate of 44735 ***
Comment 2 Marcus Schlueter CLA 2004-01-30 11:38:56 EST
My workspace is not on a nfs drive, it is local on my harddrive 
Comment 3 Rafael Chaves CLA 2004-01-30 11:51:01 EST
Could you try the test case that appears in bug 44487 comment 9 and tell us what
happens?

If that does not work for you, then, for some reason, Java file locking does not
work on your platform. The alternative would be to disable file locking by
passing the "org.eclipse.core.runtime.ignoreLockFile" property:

eclipse -vm <JAVA_HOME>/bin/java -vmargs -Dorg.eclipse.core.runtime.ignoreLockFile
Comment 4 Marcus Schlueter CLA 2004-01-30 12:17:43 EST
With the testprog i get the following output: 
 
bash-2.05b$ java TestLock /tmp/bar.txt 
trying to acquire lock once 
Exception in thread "main" java.io.IOException: Value too large for defined 
data type 
        at sun.nio.ch.FileChannelImpl.lock0(Native Method) 
        at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:788) 
        at java.nio.channels.FileChannel.tryLock(FileChannel.java:967) 
        at TestLock.acquireLock(TestLock.java:8) 
        at TestLock.main(TestLock.java:14) 
bash-2.05b$ 
 
after this i tried to start with the ignore lockfile args but eclipse won't 
start with the same error. 
 
Comment 5 Rafael Chaves CLA 2004-01-30 13:11:16 EST
That confirms that the problem is caused by the VM/OS implementation of file
locking, and you will be forced to disable the locking capability in Eclipse.

About you not being able to disable file locking: you must ensure that the
property is specified after -vmargs, because it is an argument to the VM. -data
and -vm are arguments to Eclipse.

<eclipse_install>/eclipse [arguments to Eclipse] -vmargs [arguments to the VM]

If it still does not work for you, could you please copy and paste the exact
command line you are using to run Eclipse? Thanks.
Comment 6 Marcus Schlueter CLA 2004-01-30 17:14:16 EST
Thanks a lot, now eclipse is starting up. 
I have to disable the filelocking and then it works