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 ------- Additional Comments From [EMAIL PROTECTED] 2002-11-25 14:54 ------- Hi, we have a similar memory leaking problem using org.apache.xalan.processor.TransformerFactoryImpl. We create Templates and store them in a cache with application scope. If a request needs to transform something, a servlet takes the Template and creates the Transformer with: transformer = template.newTransformer(). After that, the transformer.transform (...,...) behaves well unless 2 concurrent Requests are running. After 2 concurrent requests one transformer keeps referenced internally and is not deleted by garbage collection. After reading other entries, i found bug #6075 and #9901 which might be the same with this one. I hope, a quick solution is to turn Xalans optimizing features (default=on) off. (see #6075, http://xml.apache.org/xalan- j/apidocs/org/apache/xalan/processor/TransformerFactoryImpl.html#FEATURE_OPTIMIZ E). Right now we try it out, but first results indicate an increase of memory consumption. If it's too much, we'll syncronize our transformation. That works, but is a bad solution (because of thread starvation). Keep in mind, that it's not org.apache.xalan.xsltc.trax.TransformerFactoryImpl, but a similar effect (and maybe the same problem).
