We have a need to generate an in-memory DOM of nearly 320,000 nodes and then
apply an XSLT transformation to it (no, there isn't another way,
unfortunately). In Xalan 2.1, it works fine, and the memory footprint,
while significant, is liveable. With 2.2D7, the memory footprint is about
40% larger, and it does not appear to be garbage collecting properly
(identical code on our end), as subsequent request generate an out-of-memory
error (with Xalan 2.1, repeated requests process without problem).
Any thoughts? Suggestions?
- Rick Bullotta
CTO
Lighthammer Software (www.lighthammer.com)
