Community
Participate
Working Groups
integration build 0530, RedHat 7.3, KDE 3, --> jre 1.4 <-- I'm hoping this is the right group to log this problem with. <g> When I first run a new install of Eclipse it shows the "wait while I finish installing" screen, and about mid-way through its appearance I get the following written to my terminal: [Fatal Error] :1:1 Content is not allowed in prolog. After a few seconds the splash is brought down and the startup process seems to continue fine. I don't know how relevant the message is. Interestingly it does NOT appear if I use jre 1.3.1.
No idea .... was there anything in .log?
No, nothing written to the log. That error message doesn't look like something that we would write.
Doesn't ring any bell, what if you start with 'java', try to disable the jit option (-inline i believe). I heard some people having issue with jit.
Starting with 'java' didn't help; in fact when I did this the [Fatal Error] resulted in program execution halting, whereas when I use the Eclipse launcher it seems to continue fine in spite of the [Fatal Error] spew. Turning off jit didn't make a difference either (-Djava.compiler=yak).
I did some digging, and it would appear the new xerces has messages that match the text you observed. So, why is xerces writing to the console???? We have cases in update where we are expecting to parse xml document but don't always get valid xml, so we are catching exceptions and retrying. This may be triggering it. However, xerces has no business writing to console.
*** Bug 18631 has been marked as a duplicate of this bug. ***
F3 candidate ----- Forwarded by John Wiegand/MIN/OTI on 06/04/2002 11:52 AM ----- From: lmartin@ca.ibm.com To: John_Wiegand@oti.com Subject: Re: [Bug 18350] error message shown during startup Hi John, Do you know if the component/plugin using the parser has registered an error handler? If you don't register one, Xerces has a backup handler that will, upon receiving an error event, write a msg to stdout. The application should register a handler and take care of the errors itself. Could you check if an application error handler is set? Thx, Lisa.
released in HEAD. Added error handler to "eat" the message. The situation was caused by retry logic in accessing an update server. When reading a directory URL, the CVS server that is hosting the example actually returns a generated html page. We try to parse it, detect problems. Xerces used to be silent about this, new xerces adds a default error handler that write to console.
