Community
Participate
Working Groups
Pardon me as I try to muddle through the circumstances of this bug: 1. I had a WSWB 3.0 build (I20040304) which worked fine on Linux on a networked drive. 2. Owing to some other network trouble, our NIS primary server was taken off-line to be rebuilt. This shouldn't be a show-stopper; other clients such as Emacs or mozilla manage to start and run fine in this environment. 3. When I restart, I get a dialog: "Problems during startup. Check the .log file in the .metadata directory of your workspace" The stack trace in .metadata/.log file is at the bottom of this message. I tried cleaning my workspace and my .configuration without success. I asked another user to try my install and they got the same thing; then they tried one of their own old installs (I20040216) and got the same thing. I tried running with a workspace on a local drive ("-data /tmp/brent"), and then I could get past this. I just tried on the latest (non-WSWB) Eclipse build (I20040310) and get a near-identical stack-trace although now I get a "JVM terminated" dialog. I do not know what Eclipse is attempting to do, but it is causing me trouble. (Trouble which Emacs and VI don't have, when reading/writing networked files.) - Brent !SESSION Mar 11, 2004 14:24:39.333 --------------------------------------------- java.fullversion=J2RE 1.4.2 IBM build cxia32dev-20040128 (JIT enabled: jitc) BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -data work8 !ENTRY reference:file:/home/bnicolle/cdt/linux_gtk/wswb-SDK- I20040304/eclipse/plugins/org.eclipse.core.runtime_3.0.0/ 0 0 Mar 11, 2004 14:24:39.334 !MESSAGE FrameworkEvent.ERROR !STACK 0 org.osgi.framework.BundleException: Exception in org.eclipse.core.internal.runtime.PlatformActivator.start() at org.eclipse.osgi.framework.internal.core.BundleContext.startActivator (BundleContext.java:1010) at org.eclipse.osgi.framework.internal.core.BundleContext.start (BundleContext.java:972) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:403) at org.eclipse.osgi.framework.internal.core.Bundle.resume (Bundle.java:407) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:1018) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles (StartLevelImpl.java:565) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL (StartLevelImpl.java:479) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel (StartLevelImpl.java:269) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.dispatchEvent (StartLevelImpl.java:439) at org.eclipse.osgi.framework.eventmgr.ListenerList.dispatchEvent (ListenerList.java:135) at org.eclipse.osgi.framework.eventmgr.EventThread$EventThreadItem.dispatchEvent (EventThread.java:59) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:118) Nested exception: java.lang.IllegalStateException: Unable to create platform lock file: /home/bnicolle/cdt/linux_gtk/wswb-SDK- I20040304/eclipse/work8/.metadata/.lock. at org.eclipse.core.internal.runtime.InternalPlatform.getMetaArea (InternalPlatform.java:346) at org.eclipse.core.internal.runtime.InternalPlatform.start (InternalPlatform.java:412) at org.eclipse.core.internal.runtime.PlatformActivator.startInternalPlatform (PlatformActivator.java:171) at org.eclipse.core.internal.runtime.PlatformActivator.start (PlatformActivator.java:53) at org.eclipse.osgi.framework.internal.core.BundleContext$1.run (BundleContext.java:993) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged (AccessController.java:350) at org.eclipse.osgi.framework.internal.core.BundleContext.startActivator (BundleContext.java:989) at org.eclipse.osgi.framework.internal.core.BundleContext.start (BundleContext.java:972) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:403) at org.eclipse.osgi.framework.internal.core.Bundle.resume (Bundle.java:407) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:1018) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles (StartLevelImpl.java:565) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL (StartLevelImpl.java:479) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel (StartLevelImpl.java:269) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.dispatchEvent (StartLevelImpl.java:439) at org.eclipse.osgi.framework.eventmgr.ListenerList.dispatchEvent (ListenerList.java:135) at org.eclipse.osgi.framework.eventmgr.EventThread$EventThreadItem.dispatchEvent (EventThread.java:59) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:118) !ENTRY reference:file:/home/bnicolle/cdt/linux_gtk/wswb-SDK- I20040304/eclipse/plugins/org.eclipse.update.configurator_3.0.0/ 0 0 Mar 11, 2004 14:24:39.360 !MESSAGE FrameworkEvent.ERROR !STACK 0 org.osgi.framework.BundleException: Exception in org.eclipse.update.internal.configurator.ConfigurationActivator.start() at org.eclipse.osgi.framework.internal.core.BundleContext.startActivator (BundleContext.java:1010) at org.eclipse.osgi.framework.internal.core.BundleContext.start (BundleContext.java:972) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:403) at org.eclipse.osgi.framework.internal.core.Bundle.resume (Bundle.java:407) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:1018) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles (StartLevelImpl.java:565) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL (StartLevelImpl.java:479) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel (StartLevelImpl.java:269) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.dispatchEvent (StartLevelImpl.java:439) at org.eclipse.osgi.framework.eventmgr.ListenerList.dispatchEvent (ListenerList.java:135) at org.eclipse.osgi.framework.eventmgr.EventThread$EventThreadItem.dispatchEvent (EventThread.java:59) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:118) Nested exception: java.lang.Exception: Can not start at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize (ConfigurationActivator.java:90) at org.eclipse.update.internal.configurator.ConfigurationActivator.start (ConfigurationActivator.java:66) at org.eclipse.osgi.framework.internal.core.BundleContext$1.run (BundleContext.java:993) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged (AccessController.java:350) at org.eclipse.osgi.framework.internal.core.BundleContext.startActivator (BundleContext.java:989) at org.eclipse.osgi.framework.internal.core.BundleContext.start (BundleContext.java:972) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:403) at org.eclipse.osgi.framework.internal.core.Bundle.resume (Bundle.java:407) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:1018) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.resumeBundles (StartLevelImpl.java:565) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.incFWSL (StartLevelImpl.java:479) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.doSetStartLevel (StartLevelImpl.java:269) at org.eclipse.osgi.framework.internal.core.StartLevelImpl.dispatchEvent (StartLevelImpl.java:439) at org.eclipse.osgi.framework.eventmgr.ListenerList.dispatchEvent (ListenerList.java:135) at org.eclipse.osgi.framework.eventmgr.EventThread$EventThreadItem.dispatchEvent (EventThread.java:59) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:118)
Eclipse acquires a lock in a special file in the workspace metadata during startup. This lock is acquired to avoid two instances of Eclipse running against the same workspace location simultaneously (what would cause data corruption). The failure you got happened probably due to some interaction between your remote file system system (NFS?) locking mechanism and NIS. The workaround when locking does not work in your setup is to disable it. You will be able to start, but you will have protection from Eclipse for preventing two instances of Eclipse on the same workspace. For more info on how to disable the metadata lock, please see bug 44735 comment 3. The reason why you got the general "JVM terminated" error dialog is covered in bug 51537. *** This bug has been marked as a duplicate of 44735 ***
I actually meant "You will be able to start, but you will have *NO* protection from Eclipse for preventing two instances of Eclipse on the same workspace."
The workaround provided gets me going again. Indeed my local lockd process looks suspicious: [158]~/cdt: ps -aux | grep lockd root 4827 0.0 0.0 0 0 ? SW Feb13 0:00 [lockd] bnicolle 26848 0.0 0.0 3680 656 pts/1 S 18:09 0:00 grep lockd I would like to see a resolution which tells me more specifically why it can't start, or perhaps warns me that it is bypassing the lock daemon and continues in some kind of fall-back mode.
