[ http://issues.apache.org/jira/browse/XERCESJ-1037?page=comments#action_59224 ] Ankit Pasricha commented on XERCESJ-1037: -----------------------------------------
I still dont believe its a Xerces problem since Xerces is only involved in adding elements to the DOM. Since the problem happens when deserializing and it gives a StackOverflowError, you could try setting the stacksize higher with the -Xss option. You may have to implement a custom serialization scheme to get around this problem since you know what/how to serialize your object while the jvm is trying to do it blindly. > Critical Object streaming error with large documents > ---------------------------------------------------- > > Key: XERCESJ-1037 > URL: http://issues.apache.org/jira/browse/XERCESJ-1037 > Project: Xerces2-J > Type: Bug > Components: DOM > Versions: 2.6.2 > Environment: Windows XP, Sun, Linux, HP > Reporter: Winfried Wasser > > When I try to stream an DOM Node (Document) with the standard Java Streaming > API (by ObjectOutputStream) I get an StackOverflowError at Documents above a > size of 600-800 (I can't determine this exactly) Elements. Sometimes I get > this error at writing the Stream otherwise I get it at reading the Document > from Stream. > Its simple testable with an large Document parsed and Serialized by an > ObjectOutputStream to an File - afterwards reading it back from this File --> > and error is there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
