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=14778>. 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=14778 "Memory Leak" in XalanJ2 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-12-03 17:01 ------- We used the Xalan 2.4.1 and collcted the profiler data again. Here are the results from profiler: Method: XSLUtility.transformUsingTemplates Execution Count : 270 Temporary Bytes : 180,224,604 Bytes Temporary Objects : 254,315 Short-lived Bytes : 180,224,604 Bytes Short-lived Objects : 254,315 Medium-lived Bytes : 0 Bytes Medium-lived Objects : 0 Long-lived Bytes : 4,228 Bytes Long-lived Objects : 53 So the Memory leak problem is no more there in this version. But we saw that the performance is decreased. We did the load test for the same screen once with xalan 2.0 and then with 2.4.1 and here is the comparision between the performance (All values in seconds) Min Avg Max Std Devi. 50th Percentile 90th Percentile Xalan 2.4.1 0.3 1.5 6.27 1.37 0.97 3.4 Xalan 2.0 0.53 0.92 2.83 0.37 0.77 1.42 I am closing this case as the Memory Leak problem is fixed and for us the performance CTQ is 9 seconds so the preformance didn't impact us.
