Subject: RE: [xsl] SAXON and heavy xml doc From: "SHEIKH Sajjad" <Sajjad.SHEIKH@xxxxxxxxxxx> Date: Thu, 27 Nov 2003 11:14:30 +0100 |
Now question is: Do I need to buy a third party VM to support my program if I do not cut the file into small pieces? -----Original Message----- From: Michael Kay [mailto:mhk@xxxxxxxxx] Sent: 27 November 2003 10:33 To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: RE: [xsl] SAXON and heavy xml doc > > The same error can also mean the xsl has an infinite loop and > eating memory continuously so what the error says is not > always the cause but the result of something in the program. > In this case simply adding more memory may not be the cure. > Yes, there is often a deeper problem when you run out of memory. But in this case, the poster told us that it went away if he made the input file smaller. Michael Kay XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list ______________________________________________________________ This message has been scanned for all viruses by BTnet VirusScreen. The service is delivered in partnership with MessageLabs. This service does not scan any password protected or encrypted attachments. If you are interested in finding out more about the service, please visit our website at http://www.btignite.com/internetservices/btnet/products_virusscreen.htm ============================================================== XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] SAXON and heavy xml doc, SHEIKH Sajjad | Thread | RE: [xsl] SAXON and heavy xml doc, Michael Kay |
Re: [xsl] parent node ??, David Carlisle | Date | [xsl] Loops and variables question, Fran |
Month |