commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Janek Bogucki <...@studylink.com>
Subject Re: SAXParseException after processing 2685 records
Date Wed, 19 Feb 2003 17:13:39 GMT
Hi John,

> From: John Pollard <jpollard@meierpollard.com>
> Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
> Date: Wed, 19 Feb 2003 16:27:31 +0000
> To: commons-user@jakarta.apache.org
> Subject: SAXParseException after processing 2685 records
> 
> I am getting the following stack trace after processing a few thousand
> records out of a file of 6000 records. It varies how far it gets
> through the file before this happens. I'm using digester 1.2 and
> beanutils 1.5. All the records in the file are the same and next time
> the same record will parse ok. The file has 165,000 lines (about 27
> lines per record).
> 
> Throwable: class org.xml.sax.SAXParseException, Error at (72511, 62:
> null
> java.lang.reflect.InvocationTargetException
> at  
> org.apache.commons.digester.Digester.createSAXException(Digester.java:20
> 33)
> at  
> org.apache.commons.digester.Digester.createSAXException(Digester.java:20
> 53)
> at  
> org.apache.commons.digester.Digester.endElement(Digester.java:833)
> at  
> org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser
> .java:432)
> at  
> org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidat
> or.java:504)
> at  
> org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.
> java:629)
> at  
> org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValida
> tor.java:2731)
> at  
> org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.ja
> va:900)
> at  
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.handleEndElement(X
> MLDocumentFragmentScannerImpl.java:1136)
> 
> Thanks
> John
> 

It might be useful to learn the cause of the InvocationTargetException. You
can access the InvocationTargetException through the getException method of
the SAXParseException object. Maybe this will help locate the problem.

-Janek


Mime
View raw message