Re: Xalan Memory Problem using JDK 1.4

[Chris McCabe]

We experienced the same problem with Xalan and JDK 1.4.  The memory 
usage just keeps increasing until you run out.  We never tracked it down 
because we switched to Saxon (for performance reasons unrelated to this 
problem) which does not have the same problem.  I'm thinking it is 
related to the huge chunks of memory that Xalan allocates and for some 
reason the garbage collector is not getting rid of them.

Chris

Cory Isaacson wrote:

When we use Xalan 2.5 with JDK 1.4 (and the Java Hotspot compiler), we 
can easily produce out of memory errors. This happens most easily with 
sorts (we sorted a medium-size document 16 times and ran out of 
memory). What is curious is we don't see garbage collection happening 
when it should, and without Hotspot we don't have this problem. Any 
ideas why this would occur? Is this a bug?
--
Chris P. McCabe               - Principal Engineer
Choice Hotels International   - Information Systems
[EMAIL PROTECTED] - 602-953-4416