Community
Participate
Working Groups
Build 20040506 When restarting self-hosting workspace, I observed the following logging during startup. I had successfully opened the same workspace with the same build before. !SESSION May 06, 2004 16:57:07.701 -------------------------------------------- - java.version=1.4.2_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -showlocation -refresh !ENTRY org.eclipse.update.configurator May 06, 2004 16:57:07.721 !MESSAGE ConfigurationParser.parse() error: !STACK 0 java.lang.IllegalArgumentException at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:691) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse (XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at org.eclipse.update.internal.configurator.ConfigurationParser.parse (ConfigurationParser.java:68) at org.eclipse.update.internal.configurator.PlatformConfiguration.loadConfig (PlatformConfiguration.java:1140) at org.eclipse.update.internal.configurator.PlatformConfiguration.initializeCurren t(PlatformConfiguration.java:701) at org.eclipse.update.internal.configurator.PlatformConfiguration.<init> (PlatformConfiguration.java:83) at org.eclipse.update.internal.configurator.PlatformConfiguration.startup (PlatformConfiguration.java:642) at org.eclipse.update.internal.configurator.ConfigurationActivator.getPlatformConf iguration(ConfigurationActivator.java:296) at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize (ConfigurationActivator.java:114) at org.eclipse.update.internal.configurator.ConfigurationActivator.start (ConfigurationActivator.java:68) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run (BundleContextImpl.java:973) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator (BundleContextImpl.java:969) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start (BundleContextImpl.java:952) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:408) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume (AbstractBundle.java:373) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:999) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles (StartLevelManager.java:571) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL (StartLevelManager.java:482) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel (StartLevelManager.java:272) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent (StartLevelManager.java:442) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent (EventManager.java:153) at org.eclipse.osgi.framework.eventmgr.EventThread$Queued.dispatchEvent (EventThread.java:56) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:107) !ENTRY org.eclipse.update.configurator May 06, 2004 16:57:07.801 !MESSAGE ConfigurationParser.parse() error: !STACK 0 java.lang.IllegalArgumentException at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:691) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse (XMLReaderImpl.java:448) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at org.eclipse.update.internal.configurator.ConfigurationParser.parse (ConfigurationParser.java:68) at org.eclipse.update.internal.configurator.PlatformConfiguration.loadConfig (PlatformConfiguration.java:1166) at org.eclipse.update.internal.configurator.PlatformConfiguration.initializeCurren t(PlatformConfiguration.java:701) at org.eclipse.update.internal.configurator.PlatformConfiguration.<init> (PlatformConfiguration.java:83) at org.eclipse.update.internal.configurator.PlatformConfiguration.startup (PlatformConfiguration.java:642) at org.eclipse.update.internal.configurator.ConfigurationActivator.getPlatformConf iguration(ConfigurationActivator.java:296) at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize (ConfigurationActivator.java:114) at org.eclipse.update.internal.configurator.ConfigurationActivator.start (ConfigurationActivator.java:68) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run (BundleContextImpl.java:973) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator (BundleContextImpl.java:969) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start (BundleContextImpl.java:952) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker (BundleHost.java:408) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume (AbstractBundle.java:373) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle (Framework.java:999) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles (StartLevelManager.java:571) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL (StartLevelManager.java:482) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel (StartLevelManager.java:272) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent (StartLevelManager.java:442) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent (EventManager.java:153) at org.eclipse.osgi.framework.eventmgr.EventThread$Queued.dispatchEvent (EventThread.java:56) at org.eclipse.osgi.framework.eventmgr.EventThread.run (EventThread.java:107)
Possibly a mangled configuration file?
I put the trace last night, based on the traces you provided for the cheetah update problem. It looks like it worked :-) I will investigate.
Philippe, were you running with an old configuration directory or was it just created? Are you running on NTFS or FAT(32) ? Can you clean the configuration folder, repeat the above and attach the configuration/org.eclipse.update folder here? Thanks!
I was reopening a self-hosting workspace (old) with latest SDK under WinXP.
Filesystem is NTFS, and I reproduce it on each startup.
Created attachment 10387 [details] Configuration folder
Created attachment 10389 [details] New configuration after cleaning up first one
Clarification. In between attachment 6 [details] and 7, I did cleanup the old configuration as suggested by Dorian. First restart didn't issue any trace. Then exited and restarted, and got exceptions back.
*** Bug 61359 has been marked as a duplicate of this bug. ***
Thanks Philippe, this helped confirm my guess: it is the date attribute that is not correctly turned into a Date object. I will create another attribute instead, to store the long integer for time, and create a Date object out of that one.
Instead of using date as string, we will be using date as time (in ms) (Date.getTime()). That should fix these issues. I still write the date of the config as string inside a comment at the very top of the file. Philippe, I wonder if this has anything to do with the cheetah bug you were seeing, but I could never reproduce.
