Hi Martin, [EMAIL PROTECTED] wrote on 03/20/2008 09:38:02 AM:
<snip/> > The stacktrace of xerces when it dies with Stack Overflow is ending at > matchString until the stack overflows: > > ... > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matchString > org.apache.xerces.impl.xpath.regex.RegularExpression.matches > org.apache.xerces.impl.xpath.regex.RegularExpression.matches > org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.getActualValue > org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.validate > org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType > org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType > org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent > org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement > org.apache.xerces.impl.xs.XMLSchemaValidator.endElement > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement > org.apache.xerces.impl. > XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument > org.apache.xerces.parsers.XML11Configuration.parse > org.apache.xerces.parsers.XML11Configuration.parse > org.apache.xerces.parsers.XMLParser.parse > org.apache.xerces.parsers.DOMParser.parse > > In order to heal the problem, I have tried to simplify the > cr:nonEmptyString type by removing all eventual restrictions (regex and > minLenght) but I'm still getting the same stack trace. You must still have a type with a pattern facet somewhere in your schema. It's not possible to get the above stack trace without one. > The problem goes away, or maybe the StackOverflow does not happen when I > shorten the CDATA section under 2000 bytes. The number 2000 here is > probably related to -Xms defined when starting JVM... > > Is this a known bug? Yes: http://issues.apache.org/jira/browse/XERCESJ-589 > Do you have any hints how to solve it? You can try working around it by increasing the size of the call stack. > thanx for your time, > Martin > > P.S. I'm using xerces 2.9.1 and Sun JDK 5 > > -- > There are no bad questions, only bad answers... Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
