Ram Krishnamoorthi wrote:
My Largest XML File is about 65 MB. I am allocating a
Heap Size of 2 GB and still not able to Transform the
Entire File. I can see that the Java Process
performing the Transformation uses about 1.7 GB during
the Transformation..and my Stylesheet does not have
any Fancy Transformation, all it does is apply the
same Template repeatedly..No Tables or Images included
as well.
I'm confused. XSLT is not about tables or images.
Increasing the Max Heap Size beyond 2 GB didnt help
either.
The Sun JVM has a hard upper limit, which used to be
1G for heap and another one for the stack.
If the XSLT processor really runs out of memory, you
should get a notice somewhere. Maybe somewhere where
you didn't look yet.
Some questions:
- What JVM are you using? Which version?
- What Xalan release are you using? How do you know you
are really using this release?
- How do you run the XSLT processor? Command line? Embedded?
- Are you sure you really mean you are running only the
transformation?
- How do you handle the output? Ordinary serializing to a
file?
You might also investigate in using a memory profiler (I
like DrMem - small, free, easy to use), or asking on the
Xalan user list.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
