Hum, i ran into this kind of issue on XRadar<http://xradar.sourceforge.net/>,
if possible can you show us XSL ? There maybe a way to reduce memory
consumption by tweaking the algorithm, or simply used instruction such as
xalan:redirect (if availaible) to create file buffer to store intermediate
data...

2009/4/2 Emmanuel Bégué <[email protected]>

> Hello,
>
> Thanks for the info; the diagnostic works and confirms
> what I had suspected:
>        java.lang.OutOfMemoryError: Java heap space
>
> The cure however doesn't work; the parameters are
> accepted (I tried other syntaxes that generated errors
> outright) but they don't change anything. I tried
> more than 768M to no avail.
>
> I also found on a page of Crane Softwrights this:
>  "The summary of parameters would look something like
>  "the following, though of course you can use any file
>  "name you wish for the log file:
>  "-Xms128M
>  "-Xmx768M
>  "-D_JAVA_OPTIONS='-Xms128M -Xmx768M'
>  "-DXSLTransformer.statsfile=c:/oo3-xslt-log.txt
>  "Interestingly, the redundant settings for memory appear
>  "to be necessary as not all installations of OpenOffice
>  "support all ways of expressing the values. Expressing
>  "them both ways appears to work in some versions of
>  "OpenOffice. If you continually get "out of Java heap
>  "space" errors, try setting the memory values using only
>  "one of the two syntaxes, and then the other. If anyone
>  "can shed light on why some settings do not work on some
>  "installations, please let us know so we can share with others."
>  http://www.cranesoftwrights.com/sales/Crane-UBLProfile/
>
> I'm using OOo 3.0.1 with JRE 1.6 and:
> - -Xmx768M alone prevents the JRE from being launched at all
> - -D_JAVA_OPTIONS='-Xms128M -Xmx768M' doesn't create problems
>  but doesn't solve the problem...
>
> What I'd like to check though is whether the parameters are
> taken into account by the JRE, but insufficient, or if they
> are not even read?
>
> Regards,
> EB
>
>
> > -----Original Message-----
> > From: G. Ken Holman
>
> [I'm forwarding this answer from G. Ken Holman to the list
> as per his request -- the list apparently rejected his
> submission].
>
>
> > >Date: Thu, 02 Apr 2009 12:53:26 -0700
> > >To: <[email protected]>
> > >From: "G. Ken Holman" <[email protected]>
> > >Subject: Re: [xml-dev] Available memory for XSLT filters
> > >
> > >You can confirm more information regarding the
> > >trigger for the error by setting up the
> > >diagnostic report file name in the Java options:
> > >
> > >    -DXSLTransformer.statsfile=c:/oo3-xslt-log.txt
> > >
> > >You can increase the memory in the Java options
> > >as well ... something along the lines of:
> > >
> > >    -D_JAVA_OPTIONS='-Xms128M -Xmx768M'
> > >
> > >I hope this helps.
> > >
> > >. . . . . . . . . . . . Ken
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Romain PELISSE,
"The trouble with having an open mind, of course, is that people will insist
on coming along and trying to put things in it" -- Terry Pratchett
http://belaran.eu/

Reply via email to