Hi Michael, thanx for your quick reply, more inline...
Michael Glavassevich wrote:
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.validateorg.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexTypeorg.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.
Strange, but logical, I will try to play with the schema some more to see whether I can get rid of it...
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
Any estimate on whether, how, when it will be fixed? If at all? It looks like it affects quite a few releases back...
Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED]
thanx, Martin -- There are no bad questions, only bad answers...
smime.p7s
Description: S/MIME Cryptographic Signature
