Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 37577 - Fails to start with following error in .log
Summary: Fails to start with following error in .log
Status: RESOLVED DUPLICATE of bug 19252
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.1   Edit
Hardware: Sun Solaris
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-13 23:30 EDT by Lubos Pochman CLA
Modified: 2003-05-14 11:54 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lubos Pochman CLA 2003-05-13 23:30:09 EDT 
Fails to start with following error in .log:

!SESSION ----------------------------------------------------------------------
!ENTRY org.eclipse.core.launcher 4 0 May 13, 2003 15:34:04.623
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.ExceptionInInitializerError
	at org.eclipse.core.internal.plugins.RegistryLoader.processManifestFile
(RegistryLoader.java:89)
	at 
org.eclipse.core.internal.plugins.RegistryLoader.processPluginPathFile
(RegistryLoader.java:136)
	at 
org.eclipse.core.internal.plugins.RegistryLoader.processPluginPathEntry
(RegistryLoader.java:127)
	at 
org.eclipse.core.internal.plugins.RegistryLoader.processManifestFiles
(RegistryLoader.java:104)
	at org.eclipse.core.internal.plugins.RegistryLoader.parseRegistry
(RegistryLoader.java:63)
	at org.eclipse.core.internal.plugins.RegistryLoader.parseRegistry
(RegistryLoader.java:71)
	at org.eclipse.core.internal.runtime.InternalPlatform.parsePlugins
(InternalPlatform.java:779)
	at org.eclipse.core.internal.runtime.InternalPlatform.loadRegistry
(InternalPlatform.java:723)
	at org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup
(InternalPlatform.java:574)
	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:1011)
	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:291)
	at org.eclipse.core.launcher.Main.run(Main.java:747)
	at org.eclipse.core.launcher.Main.main(Main.java:583)
Caused by: java.lang.ClassCastException
	at org.apache.xerces.parsers.SAXParser.<init>(SAXParser.java:95)
	at org.eclipse.core.internal.plugins.PluginParser.initializeParser
(PluginParser.java:80)
	at org.eclipse.core.internal.plugins.PluginParser.<clinit>
(PluginParser.java:44)
	... 23 more
Comment 1 Rafael Chaves CLA 2003-05-14 11:07:48 EDT 
This is a known problem that happens when Eclipse finds a different version of 
Xerces in the boot classpath than the one it comes with.

For more info, see bug 19252 and its duplicates.

You may want to see also:

http://eclipsewiki.swiki.net/134#badXerces

*** This bug has been marked as a duplicate of 19252 ***
Comment 2 Lubos Pochman CLA 2003-05-14 11:54:44 EDT 
Yep, the advice in wiki fixed it. Thanks, will check next time.