IPlanet 6.0 SAX parser fatal error

I am getting the following error, at the start of iPlanet 6.0 web server. The line number 5 is <!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
in the file web.xml
Error message in iPlanet:
failure ( 1608): vs(https-CLV-EATON)SAX parser fatal error: External entity not found: "http://java.sun.com/dtd/web-app_2_3.dtd". in file:/c:/iPlanet/Servers/docs/EatonIP/WEB-INF/web.xml at line number 5. [30/Jul/2002:18:25:09] warning ( 1608): vs(https-CLV-EATON)Error parsing web-app deployment descriptor c:\iPlanet\Servers\docs\EatonIP\WEB-INF\web.xml: External entity not found: "http://java.sun.com/dtd/web-app_2_3.dtd".
Any help is appreciated.

Hi,
I'm facing same problem with iPlanet. I want to add <listener> in web.xml file. My web server has web-app_2_2.dtd file. But this file don't have entry for <listener>, then I found that web-app_2_3.dtd has this entry. I have to use this file. I'm using iPlanet 6.
So please let me know that how I do that ?
Can I add new DTD file to Web Server ? How ?
Can I install any patch to have web-app_2_3.dtd file on Web Server ?
U can send me mail on [email protected]
This is how my web.xml file is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<listener>
<listener-class>CRSSessionListener</listener-class>
</listener>
</web-app>
Whenever I include web-app_2_3.dtd file in web.xml, I'm getting error that 'External entity 'web-app_2_3.dtd' not found. And if I'm not using web-app_2_3.dtd file then web server could not parse web.xml file.
If u have found the solution can u mail me [email protected]
Thanx in advance,
~Abhijeet

Similar Messages

Trying to create a pdf with jasper - Parse Fatal Error at line 1 column 1:

29/11/2007 16:52:03 org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:215)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:386)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
     at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1438)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:899)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
     at org.apache.commons.digester.Digester.parse(Digester.java:1666)
     at net.sf.jasperreports.engine.xml.JRPrintXmlLoader.loadXML(JRPrintXmlLoader.java:151)
     at net.sf.jasperreports.engine.xml.JRPrintXmlLoader.load(JRPrintXmlLoader.java:103)
     at net.sf.jasperreports.view.JRViewer.loadReport(JRViewer.java:1376)
     at net.sf.jasperreports.view.JRViewer.<init>(JRViewer.java:243)
     at net.sf.jasperreports.view.JRViewer.<init>(JRViewer.java:214)
     at net.sf.jasperreports.view.JasperViewer.<init>(JasperViewer.java:140)
     at net.sf.jasperreports.view.JasperViewer.viewReport(JasperViewer.java:397)
     at net.sf.jasperreports.view.JasperViewer.viewReport(JasperViewer.java:328)
     at br.com.abril.contratos.Gerar.geraRelatorio(Gerar.java:38)
     at br.com.abril.contratos.Gerar.main(Gerar.java:47)

The XML file that you're reading has something before the first line - either a comment, whitespace, or other characters. The first characters of your XML file MUST be the XML declaration:
<?xml ...
If there's anything before that angle bracket it's not valid XML.

XML parsing fatal error [subject edited by moderator]

Hello, when I try to open dreamweaver CS 5 I have this message: XML parsing fatal error: Invalid document structure, line: 1, File:C:\Users\Jean\AppData\Roaming\Adobe\Dreamweaver CS5\fr_FR\configuration\Workspace\Designer.xml Please help me.
Thank you to help me for this question about fatal error.

Deleting a corrupted cache file

Dreamweaver stopped working. XML parsing fatal error: Invalid document structure, line1 Tried reloading DW. Didn't work.

Dreamweaver (CS5) stopped working. The error message says - XML parsing fatal error: Invalid document structure, line: 1, I tried to reload DW. No change. I also tried to reset the computer to an earlier date before I reloaded. Also didn't work. Can anybody shed some light?

The first thing to try is Deleting Corrupted Cache. Be sure to turn on Hidden Files & Folders in your file manager (Win Explorer or Mac Finder).
http://forums.adobe.com/thread/494811
If that doesn't help, try Restore Preferences
http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html
If all else fails, use the CC Cleaner Tools below to wipe DW from your system, followed by a software re-install.
http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
Keep us posted on your results.
Nancy O.

XML parsing fatal error: Invalid document structure, line: 1, file: ... (in this case "Classic.xml"

dreamweaver not initiating..claiming a parsing fatal cerr because classic.xml is corrupted. I tried re-installing dreamweaver... nothing

See here Dreamweaver CS5 fatal error XML parsing: Invalid document structure, line:1, File: C:\User\Tyler\App

Adobe Flash Cs4 : xml parsing fatal error invalid document structure line 1 file

Hi there.. Well, this is in the title.. I got a problem with adobe flash cs4 : I can't launch it normaly and its says that a fatal error has occured.. I really don't know what I must do.. Please, help me.... I've just lost like 3 or 4 files of adobe by trying to reinstall it.. Help me please..
** My tools are now invisible **

Say do you have a designer.xml file

Dreamweaver cs5 : cant launch it suddenly due to XML parsing fatal error. WHY ?

System asked me to load a correct layout from WINDOWS - WORKSPACE
1/ it was not like that yesterday
2/ from the folder window ,I could not
find any file named WORKSPACE
* MY o/s - Windows 7
==> should I re-install dreamweaver first before doing anything ?
==> how can I load that layout ?
3/ my dreamweaver cs3 is no problem

before I noted your comments,I uninstalled it already.
Last time I failed after uninstalling & reinstalling it probably
becos I forgot to restart the computer.
Now , it resumes normal

Fatal error in Java Parser V2 :Status??

We still have a problem with entity references
in V2 of the JAVA XML parser (see Rolf van Deuresen 24-11).
It is a very urgent problem for us. We think that the XML-team
is working on it. Can you inform me abouth the status with the
(bug??)-fix. If you need more information on the problem, please
ask.
Greetings,
Erik van den Berg.
null

Attachments: "1|type=text/plain|desc=SAXSample output|17142|file=output.txt|"
Oracle XML Team wrote:
: Erik van den Berg (guest) wrote:
: : Oracle XML Team wrote:
: : : Erik van den Berg (guest) wrote:
: : : : We still have a problem with entity references
: : : : in V2 of the JAVA XML parser (see Rolf van Deuresen 24-
11).
: : : : It is a very urgent problem for us. We think that the
XML-
: : team
: : : : is working on it. Can you inform me abouth the status
with
: : the
: : : : (bug??)-fix. If you need more information on the
problem,
: : : please
: : : : ask.
: : : : Greetings,
: : : : Erik van den Berg.
: : : Have you downloaded the latest version 2.0.2.5 that was
made
: : : available this week?
: : : Oracle XML Team
: : : http://technet.oracle.com
: : : Oracle Technology Network
: : I have downloaded the new version 2.0.2.5 of the Java
parser,
: : and it stil doesn't work. Please refer to the original
message
: : from Rolf van Deursen (24th november 1999) for the details.
: : Maybe it will help you if I mail you a XML file that fails.
If
: : so, please give me your email account.
: : Greetings,
: : Erik van den Berg.
: You can attach files to messages in the forum here.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
Here's the XML that raises the Fatal error. The following
information is generated by the parser:
Fatal Error of Java SAX parser v2.0.2.5:
XML-0121: (Fatal Error) End tag does not match start
tag 'WOONPLAATS'. at line 517, column 4151 of XML document.
I attached the output of the SAXSample class, so you can trace
the line and column where the error occurs. Also attached is the
XML file (4Mb).
An other error that occurs with this XML is the following
situation:
<VOLGNR_FILM> 001</VOLGNR_FILM>
this piece of XML is parsed with the following events:
StartElement:VOLGNR_FILM
Characters:NR_
Characters:001
EndElement:VOLGNR_FILM
So the spaces are replace with a part of the start tag! This is
also only with large files. I tested this piece of XML in a
seperate file. Then it was parsed correctly.
Kind regards,
Erik.
null

Dreamweaver CS5 Fatal Error XML Parsing

Can anyone help me with CS5 dreamweaver - It has a fatal error on windows 7 - it states XML Parsing fatal error an exception occurred, Type: unexpected of exception message: the end of input was not expected, line 22 file: c\users\danny\appdata\roaming\adobe\dreamweaver cs5\en_us\configuration\workspace\designer.xml.
I cannot use dreamweaver at all - PLEASE HELP ME. Thanks

The xml file which defines the Workspace layout has become corrupt.
Navigate to the file via the path listed in your post, delete it and relaunch Dreamweaver.
http://forums.adobe.com/message/2124385
If Dreamweaver still won't launch. delete the entire Configuration folder. Dreamweaver should then create a fresh Configuration folder the next time you launch it.
Locating your personal configuration folder
http://forums.adobe.com/thread/494812

Dreamweaver CS5 fatal error XML parsing: Invalid document structure, line:1, File: C:\User\Tyler\App

XML parsing fatal error: Invalid document structure, line: 1, file: C:\User\Tyler\AppData\Roaming\Adobe\Dreamweaver CS5\en_US\Configureation\Workspace\Classic.xml
I have gone through older disscussion forums and have followed the steps recommended by deleting the corrupted .xml file itself (in this case "Classic.xml") but imidiatly after when i try to open Dreamweaver again, i am prompted with the same fatal error message including the file that i have just deleted. Next i deleted the entire configure file and this did not help either.
It is also odd that when i follow the path to find the corrupted .xml file from the prompt, the path is different in that i do not find the "Classic.xml" file through th "en_US\Configuration\Weorkspace" navigation, however i do find the corrupt "Classic.xml" file in the "configure" folder of the "Adobe Dreamweaver CS5" file.
Im not sure what to do now and i would really like Dreamweaver back up and running so please help if you can!!!
Thanks
-Tyler

Step 1: Close DW, Navigate to C:\User\Tyler\AppData\Roaming\Adobe\Dreamweaver CS5\en_US\Configureation\Workspace\ and delete that Classic.xml file
Re-open DW. DW should auto-create your Workspace layout XML file again. See if it works fine.
PROCEED TO STEP 2 ONLY IF STEP 1 DOESN'T SOLVE THE ISSUE
Step 2: Navigate to C:\Users\Tyler\AppData\Roaming\Adobe\Dreamweaver CS5\en-US\Configuration and delete the entire 'CONFIGURATION' folder. Re-open DW. DW should auto-create your configuration folder based on predefined layouts and config options. This will definitely fix your issue.
Reason for this issue: This issue would have been caused due to a malformed workspace layout configuration. That may happen due to customizations you may have done to the layout/ improper file permissions/ improper shutdown on Windows.
See if these fixes resolve your issue and post your results here.
Cheers,
ST

SAX Parser,setValidationMode

We have to parse an XML of 5 MB size and load into the
Database.We started using the DOM Parser(PL/SQL) and getting the
Out of Memory errors.(The Java Pool Size is 250 MB).As per the
Oracle Documentation we have stated using the SAX Parser.But
Using SAXParser we are not able to use the "setValidationMode"
Method.I am getting "Method setValidationMode(boolean) not found
in interface org.xml.sax.Parser." error message.
Can any one help me what is the problem.
Thanks in Advance.

SAX should mask the fact that some content is specified inside of a CDATA section.. It is just characters.
The safest way to process characters is to setup a StringBuffer or equivalent in the startElement method. There is a variation of the StringBuffer append method that has the same three parameters (char[], int, int) as the characters signature. The characters method may be called many times before you are given all of the content of the string. How it decides when to call you depends on the parser and is subject to change over time. But, if you accumulate the contents in each call of characters and do the toString() in the endElement method you are going to get the right content. Lots of people over the last year or so that I've been involved in this forum have had other ways they thought were better than this, but most of them have eventually tried and accepted this way because it works and their "better" way did not.
It looks like you got the content for the CDATA section (Please refer...).I'm not sure what your problem is.
Dave Patterson

Fatal error XML-0121 in a valid XML file in v2 of SAX parser

Attachments: "1|type=text/plain|desc=Logging of Fatal error using v2 of SAX parser |file=v2_loggin
.txt|";"2|type=text/plain|desc=Logging of Fatal error using v2 of java SAX parser |17078|file=v2_l
gging.txt|"
Dear XML team,
I am using the SAX parser version 2.0.2.4. When parsing a valid
XML of approx. 3,5 Megabytes i get a fatal error XML-0121
saying 'End tag does not match start tag
<CORRESPONDENTIENAAM1>...'
We checked the xml on the well formedness with tools like XML
Spy and IE5. The XML is valid!
We did some testing on the XML with the SAXSample class and we
noticed that the error is related to the use of Entity
References. When we removed the Entity Reference ' the XML
was parsed correctly.
We also noticed that if we cut the XML in two smaller parts it
was also parsed correctly.
I attached the output of the parser, as well as the output of
the SAXSample class.
I hope you can fix this problem!
With kind regards,
Rolf van Deursen.
null

Update: I have attempted to use xmlparserv2.jar dated 12/23/08 that is packaged with jDeveloper 11g preview, but am still receiving the same message.

Org.xml.sax.SAXParseException: Line 1, Column 1 : XML-0108: (Fatal Error)

Hi ,
I am using SAX parser in a java code , which compiles and parses an xml correctly in the local JVM.
But the same code in OC4J(10g) - version 9.0.4.2 throws the following exception when traced the error stack.
08/04/04 17:48:40 Loading file workingday.xml from directory ========================== :::java.io.BufferedInputStream@bd4e3c
08/04/04 17:48:40 Read the xml into instream => STEP II
08/04/04 17:48:40 Read the xml into instream => STEP II
08/04/04 17:48:40 adding to the bankholiday list
org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-0108: (Fatal Error) Start of root element expected.
08/04/04 17:48:40 at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:226)
08/04/04 17:48:40 at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:162)
08/04/04 17:48:40 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:305)
08/04/04 17:48:40 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:267)
08/04/04 17:48:40 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
08/04/04 17:48:40 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:286)
08/04/04 17:48:40 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:224)
Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server and throwing the above error for an xml , which is absolutely alright.
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.parsers.SAXParser;
import javax.xml.parsers.SAXParserFactory;
Please let me know why this happens? Is it a known bug in the OC4J 9.0.4.2?
Thanks and Regards
Antara

hi Antara
about "... Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server ..."
If you have used the SAXParserFactory.newSAXParser() method to get a parser, the documentation for this method says "Creates a new instance of a SAXParser using the currently configured factory parameters.".
So you might get a different parser in a different environment.
regards
Jan Vervecken

Problem in error handling in SAX Parser

My application takes xml message as input.
If a error was found while validating, an <Errors> <Error></Error></Errors> element is included in the orginal message and send back to the user.
While validation xml message I found an interesting problem.
Created a false entry for the root element attribute.
Traced method invocation.
First the call back error method is invoked,then the start element(stored the attributes inside the starElement to a instance variable).When i tried to print the attribute .As the error method got invoked first
if showed "null".
But when i created the same case with the child elements attributes
even though invoking of the methods happens in the same sequence
attributes got assigned and can print the attibutes values.
xml is schema vaidated .Is there any restriction that root element should not contain attributes.Can any one explain how the call back methods are invoked .
Regards
Dheeraj
// import statements here
public class OperationHandler extends DefaultHandler {
     private static Logger logger = Logger.getLogger(OperationHandler.class.getName());
     private Attributes attributes;
     private StringBuffer dataStore;
public OperationHandler() {
dataStore = new StringBuffer(100);
     * Receive notification of the end of an document.
     public void startDocument() {
          logger.debug("OperationHandler: startDocument");
     * Receive notification of the beginning of the element.
     public void startElement(String uri, String lName,
                                        String qName, Attributes attributes) {
          logger.debug("OperationHandler: startElement" + lName);
          dataStore.setLength(0);
     * Receive notification of the end of an element.
     public void endElement(String uri, String lName, String qName) {
          logger.debug("OperationHandler: endElement");
          // bussiness specific code
     * Receive notification of the end of an document.
     public void endDocument() {
          logger.debug("OperationHandler: endDocument");
     public void error(SAXParseException saxe) {
          logger.debug("OperationHandler : error");
          System.out.println("CurrentElement"+currentElement +" "+"Attributes" + attributes);
               if(attributes != null) {
                    for(int i=0; i < attributes.getLength(); i++) {
                         System.out.println(saxe.getColumnNumber());
                         System.out.println(saxe.getLineNumber());
                         System.out.println(saxe.getMessage());
     public void fatalError(SAXParseException saxe) throws SAXException {
          logger.debug("Fatal error while parsing message");
          logger.error("Error " + saxe.getMessage() );
     public void warning(SAXParseException saxe) throws SAXException {
          logger.warn("Warning " + saxe.getMessage() );
     * Receive notification of character data inside an element.
     public void characters(char[] charData,int start, int length) {
          String strData = new String(charData, start, length);
          if(strData != null) {
               strData.trim();
               dataStore.append(strData);
}

Hi Muruganand,
Is the data load failing while loading data or while activating?
if the data load is failing at activation, thers is nothing you can do except editing the records in PSA and then update them.
As far as i have seen, the data load to DSO fails in Activation and not while loading. this is the reason why the records are not collected in error stack
unlike if it is a cube, the data load fails while loading collecting the recods in error stack.
hope this helps,
Thanks and Regards,
Srinath.

Error Error oracle.iam.platform.context.ContextManager BEA-000000 IAM-0030007 org.xml.sax.SAXParseException: Line 1, Column 1 : XML-20108: (Fatal Error) Start of root element expected. error in oim logs

Hi ,
I am getting the below error at times in oim logs not able to find the reason please help.
<Error> <oracle.iam.platform.context.ContextManager> <BEA-000000> <IAM-0030007
org.xml.sax.SAXParseException: <Line 1, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
    at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
<XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/bindToInstance encounter some problems: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
oracle.iam.platform.utils.ServiceInitializationException: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    at oracle.iam.platform.Platform.getService(Platform.java:265)
    at oracle.iam.platform.OIMInternalClient.getService(OIMInternalClient.java:188)
    at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(tcDataBaseClient.java:151)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.recoverConnection(tcDataBaseClient.java:401)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.getInterface(tcDataBaseClient.java:385)
    at com.thortech.xl.dataaccess.tcDataBaseClient.close(tcDataBaseClient.java:349)
    at com.thortech.xl.server.tcDataBaseClient.close(tcDataBaseClient.java:62)
    at com.thortech.xl.server.tcDataBaseClient.finalize(tcDataBaseClient.java:43
Caused By: java.lang.ClassNotFoundException: weblogic/jndi/WLInitialContextFactory
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at com.sun.naming.internal.VersionHelper12.loadClass(Ve
<Class/Method: tcDataBaseClient/getInterface encounter some problems: RuntimeException encountered. Reconnecting!
java.lang.NullPointerException
    at oracle.iam.platform.context.ContextManager.getCounter(ContextManager.java:697)
    at oracle.iam.platform.context.ContextManager.incrementCounter(ContextManager.java:684)
<Error> <XELLERATE.DATABASE> <BEA-000000> <Class/Method: tcDataBaseClient/close encounter some problems: Bean has been deleted.
javax.ejb.NoSuchEJBException: Bean has been deleted.
Thanks,
Sahana

hi Antara
about "... Though I have imported the following JDK parsers in the code , the Oracle's SAX parser is taking other inside the application server ..."
If you have used the SAXParserFactory.newSAXParser() method to get a parser, the documentation for this method says "Creates a new instance of a SAXParser using the currently configured factory parameters.".
So you might get a different parser in a different environment.
regards
Jan Vervecken

IPlanet 6.0 SAX parser fatal error

Similar Messages

Maybe you are looking for