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-02-28 22:01 ------- One idea: If you're using variables containing Tree Fragments, the DTMs containing those fragments may not be released until after the XRTreeFrag objects have been garbage collected. I'm somewhat astounded that you're managing to run out of DTM IDs even so -- current code can have 2**16 DTM IDs open at once, though if you have large documents a single DTM may require multiple IDs. Since you said you're using Xalan 2.2, I'd suggest you try 2.3 and see whether the situation persists. Actually, if possible I'd suggest you try current CVS code, since we recently fixed a reentrancy issue related to XRTreeFrag's finalizers.
