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=6750>. 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=6750 Reusing a Transformer causes a NullPointerException ------- Additional Comments From [EMAIL PROTECTED] 2002-02-28 15:43 ------- Unfortunately, the bug does not appear to be resolved in the latest build. I tried running the test case against a xalan.jar I compiled myself from xml- xalan_20020228051849. I also tried it using the xalan.jar included with the xalan-j_20020227 binary build. This is a tough bug to reproduce. The variables introduced by differing jvm garbage collection algorithms, different os thread implementations, etc, seem to make big differences. I've reproduced the problem in a wide range of environments (listed below), and it appears that the test case I provided fails the fastest : 1. using a maximum heap size of 1 meg. (-Xmx1M) 2. using the IBM jdk, or using a pre-1.4 Sun jdk with (-Xincgc) 3. if the xslt script contains a larger number of <xsl:value-of select="$recSep"> lines. If you take the sample provided and add another 500 copies of this select statement it seems to fail faster in more environments. The environments I've tested on include * linux 2.2.13 using sun jdk 1.3.1_02 (the latest) * linux 2.4.7 using ibm jdk 1.3 * linux 2.4.7 using ibm jdk 1.3.1_02 * Windows 2000 using ibm jdk 1.3.0 * Windows 2000 using sun jdk 1.3.1 Interestingly....I can't seem to reproduce the problem using the sun jdk 1.4.
