XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Java Runtime Environment boot ... (2)
-> + Associate XML with Schema (3)
-> + JVM not found in stylus studio... (2)
-> + Change newline to Linux (on Wi... (4)
-> + Indent XML Tags only partially... (2)
-> + dealing with invalid character... (2)
-> + Unable to call Webservice thro... (2)
-> + XML to CSV Video create csv te... (5)
-> + Try to test this product, (2)
-> + How to migrate license? (3)
-> - kepp your settings on X15 upda... (1)
-> + No Topic (2)
-> - XSD validation scalability iss... (2)
-> ->XSD validation scalabilit...
-> + Installing documentation in ai... (4)
-> + Stylus Studio is currently una... (2)
-> + Change from SS Pro 2011 to SS ... (2)
-> + Problem with pipeline function... (2)
-> + Min and Max Occurs for Choices... (2)
-> + XSLT without Preview window ou... (3)
-> + How to achieve this transforma... (2)
-- Previous [241-260] [261-280] [281-300] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Yitzhak KhabinskySubject: XSD validation scalability issue
Author: Yitzhak Khabinsky
Date: 04 Dec 2012 10:57 AM
Originally Posted: 04 Dec 2012 10:40 AM
Hello,

My environment:
• SS X14 R2 Enterprise Suite build 1893h
• OS: Windows 7 64-bit
• RAM: 12 GB
• Java: Java 7 update 9
• Java Virtual machine parameters: -Xms8m -Xmx64m -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

I am trying to run XSD validation for 118 MB file size XML file.
Both Saxonica 9.4.0.6 and Java built-in validators producing an error.
My next step was to comment out 99.99% of the XML and re-run the XSD validation. Alas, the same outcome – XSD validation error.
It seems that the mentioned above XSD validators still loading even commented out nodes of the XML in the DOM.

Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.stylusstudio.debugger.saxon.Validate.main(Validate.java:93)
Caused by: java.lang.OutOfMemoryError: Java heap space
at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.scanComment(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanComment(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:405)
at net.sf.saxon.event.Sender.send(Sender.java:152)
at com.saxonica.Validate.processFile(Validate.java:514)
at com.saxonica.Validate.doValidate(Validate.java:347)
at com.saxonica.Validate.main(Validate.java:62)
... 5 more

P.S. I prefer to use Saxonica validator because of its detailed validation information

The test case is in the attachment.


DocumentXSDValidationScalabilityIssue.zip
Test case for XSD validation

Posttop
Ivan PedruzziSubject: XSD validation scalability issue
Author: Ivan Pedruzzi
Date: 20 Jan 2013 12:33 AM

The out of memory error was caused by a very large section of the XML document that was inside a comment. Saxon validates using a SAX filter which materializes comments as text nodes in memory.

Ivan Pedruzzi
Stylus Studio Team

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.