Hi Paul, This happens because you have maxOccurs="50000" on " originDestinationPair". The larger the value of maxOccurs the more memory Xerces requires to build the DFA representation of the content model. If the value is sufficiently large you'll run out of memory. The workaround for this limitation [1] has always been to change large maxOccurs values to unbounded.
Thanks. [1] http://xerces.apache.org/xerces2-j/xml-schema.html Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] "Paul Tomsic" <[EMAIL PROTECTED]> wrote on 10/27/2006 05:42:36 PM: > I think i've found a bug in xerces 2.8.1. > I've attached a tarball that reproduces the error. > The error is "OutOfMemoryError: Java heap space" > > the situation is an XML file points to a XSD which contains several > "included" XSDs. > one of those XSD's has a mismatched targetNamespace. > > While stepping thru the code in a debugger, it does find the problem > and record the correct SAXParseException, but it continues to traverse > the tree of included XSDs, thus causing the heap space out of memory > situation. > > hopefully it's something that i'm doing wrong, though. any thoughts helpful. > > To run the attached tarball, simply expand it, load up the "lib" directory w/ > -xercesImpl 2.8.1 > -xml-apis 2.8.1 > -resolver - the version that ships w/ xerces 2.8.1 > > then run the "run.sh" shell script. > > thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
