Title: RE: Passing large XML Document object via RMI

We used to get this when parsing and processing very large DTDs (like DocBook) when we switched to Xerces2.

I know it seems like a terrible hack, but using -mx256M on the Java commandline solved the problem.

John

-----Original Message-----
From: Mark Gertsvolf [mailto:[EMAIL PROTECTED]]
Sent: 16 June 2002 15:43
To: [EMAIL PROTECTED]
Subject: Passing large XML Document object via RMI


Hello everybody,

While using Xerces-J version 2.0.1.
I am having a problem with passing a large XML Document via RMI. The
receiving side gets a "Stack overflow" exception.
Some of the resources on the web suggest that it is a serialization
issue (the serialization being a recursive process causes stack overflow
on a large hierarchy of objects, which DocumentImpl object is). The
solution is to overwrite writeObject/readObject methods of the object in
question using intimate knowledge of the object.

Has anybody had such an issue in the past and what is the solution.

Your help is much appreciated.
Mark Gertsvolf



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential.  Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message.

Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses.

Reply via email to