Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330193

Summary: running error at startup
Product: [Eclipse Project] Platform Reporter: ML <m.landrain>
Component: RuntimeAssignee: platform-runtime-inbox <platform-runtime-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: gary.newbould, pwebster, remy.suen
Version: 3.6.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Log ficle Eclipse
none
The File log Eclipse none

Description ML CLA 2010-11-14 04:54:43 EST 
Build Identifier: eclipse-SDK-3.6.1-win32.zip

An error occures when eclipse 3.6.1 is starting.

Here is the beginning of the log eclipse message :

!SESSION 2010-11-14 08:53:26.734 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2010-11-14 08:53:32.875
!MESSAGE An unexpected runtime error has occurred.
!STACK 0
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
	at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook$ParsingService.createService(EclipseAdaptorHook.java:147)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook$ParsingService.getService(EclipseAdaptorHook.java:139)


Reproducible: Always

Steps to Reproduce:
1.Click on the executable file : eclipse.exe.
Comment 1 ML CLA 2010-11-14 05:05:28 EST 
Created attachment 183090 [details]
Log ficle Eclipse

Here is the log file created when eclipse is starting
Comment 2 Remy Suen CLA 2010-11-14 06:50:49 EST 
Could you try uninstalling and then reinstalling your JRE?
Comment 3 ML CLA 2010-11-14 15:53:09 EST 
(In reply to comment #2)
> Could you try uninstalling and then reinstalling your JRE?

Thank's for your Feed back.

The JRE has been uninstalled, and after installed again.
The same error still appens.

I decided to install amore recent java version (update 22), and I obtain the error above :

!SESSION 2010-11-14 21:24:46.547 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_22
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.equinox.p2.core 4 0 2010-11-14 21:24:48.266
!MESSAGE Provisioning exception
!STACK 1

Thank's for your help.
Comment 4 ML CLA 2010-11-14 15:57:40 EST 
Created attachment 183096 [details]
The File log Eclipse
Comment 5 Darin Wright CLA 2010-11-14 17:20:46 EST 
Moving to runtime
Comment 6 John Arthorne CLA 2010-12-15 12:00:11 EST 
*** Bug 331433 has been marked as a duplicate of this bug. ***
Comment 7 John Arthorne CLA 2010-12-15 12:03:33 EST 
This comment from bug 301815 might be helpful to people:

After a longer investigation I found an xerces.jar library from 2003 in 
/Users/username/Library/Java/Extensions
which survived several os and hardware upgrades.

In short, this appears to be a JRE configuration problem, that can be solved by ensuring you have a clean JVM install with no old copies of libraries lying around.
Comment 8 Eclipse Webmaster CLA 2019-09-06 16:06:52 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 9 Eclipse Genie CLA 2022-02-23 19:29:56 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.