DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6768>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6768 High Xms heap settings in JVM produce org.apache.xml.dtm.DTMException: No more DTM IDs are available. ------- Additional Comments From [EMAIL PROTECTED] 2002-03-08 13:39 ------- Ok. I tested the System.gc() bit using the following: { System.gc(); System.runFinalization(); System.gc(); } Calling this before calling Xalan doesn't improve things, so it's a single transformation that causes the trouble. It just happened to be the fourth transformation (as the fourth screen is always the most complicated in this particular application I guess). A quick fix (so i didn't have to rebuild Xalan) was to run the above in a seperate Thread during the execution of Xalan (using an interval so it get's run at least once during the xalan execution) did solve the problem, so you're right about the finalizers that need to be run to clean things up. So I guess that the quick-fix for xalan would be to try the above before running out of DTM id's. Please note though, that System.gc() and the forced finalization have a huge performance impact.
