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=9781>. 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=9781 No more DTM IDs are available [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-02 13:24 ------- It seems that the bug is still present. I experienced it on my project using Xalan-J 2.4.0 and J2sdk 1.4.1. It finally managed to simplify the transformation to get a test case. So, I reopen this bug and will attach the test case : testCase.xsl : the xsl file input.xml : the input xml file testCase.bat : the command to launch the transformation On my machine (jdk 1.4.1, Windows 2000), the output is (Location of error unknown)XSLT Error (javax.xml.transform.TransformerException) : org.apache.xml.dtm.DTMException: No more DTM IDs are available Note that : - the java option -ms150m seems to play a role since it is required to reproduce the bug - input.xml contains 1750 nodes. If you lower this number to about 1000 nodes, then the bug will not happen anymore - bug #6768 is very similar. Isn't it a duplicate ? I hope that this will help you track and fix the bug, as it is now a major problem in my project. Thanks for you efforts, Denis Genard
