Here is the TestXalan.java. By the way, we are sure we didn't reuse it across multiple threads...
Actually, further investigation shown that the resource are being kept by the axes's iterator pool. It seems like Xalan try to cache the iterator, and reuse it later on. However, the problem is, since the iterator is cached, the underlying "TransformerImpl" is also kept in the sense that it will hang on to the ResultStream's stream. My 2 cents is: Caching an iterator is a good idea, as long as it free it's underlying resource... Thanks. William. -----Original Message----- From: Shane Curcuru [mailto:[EMAIL PROTECTED] Sent: Thursday, January 24, 2002 12:42 PM To: [EMAIL PROTECTED] Subject: Re: Memory leak or threading problem in Xalan-J 2.2? Two questions: - Could you be re-using the same Transformer object (or derivative) across multiple threads? Transformers are not threadsafe - only Templates objects are. - You need to re-send the TestXalan.java program either as an attachment or inline, since that 3rd attachment doesn't seem to have made it to the list. - Shane ===== <eof aka="mailto:[EMAIL PROTECTED]" "http://www.otnemem.com/"=.sig /> __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you.
TestXalan.java
Description: Binary data
