Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Message-ID: <429AC26F.1060804@apache.org>
Date: Mon, 30 May 2005 09:36:15 +0200
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Possible memory leak when handle-errors is called
References: <429822AA.1010909@apache.org> <42998DE5.7050603@apache.org>
 <4299C9F0.8090401@apache.org> <429ABE85.30105@apache.org>
In-Reply-To: <429ABE85.30105@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Carsten Ziegeler wrote:
> Reinhard Poetz wrote:
> 
> 
>>AFAICS the usual behaviour is that there is only one TraxTransformer Object, 
>>independently from the number of requests and different stylesheets. 
> 
> Hmm
> 
> 
>>As soon as
>>I call URIs that cause "handle-error" sections, new TraxTransformer objects are 
>>created, when the handle-error sections contains an error. Setting the 
>>"pool-max" attribute doesn't change this. AFAICS the TraxTransformer (+ all the 
>>Xalan stuff) don't get garbage collected.
> 
> So, is the "recycle()" method of the TraxTransformer called?

not when the TraxTransformer is used in "handle-errors"-sections, in usual 
pipelines yes. What's the difference?

-- 
Reinhard P�tz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

	

	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de