cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stuart Roebuck <>
Subject Re: [C2] Possible bug in ?
Date Thu, 02 Aug 2001 21:09:37 GMT
Okay, at last I think I've fixed this problem.  Thank you Vadim for making 
me aware that components could have individual pool settings.  Many days 
later and many false leads past I now have a ridiculously simple solution.

I think it would be a very helpful idea to include at least one use of 
these individual component pooling settings in the example sitemap just to 
let people know the facility is there.

All I needed to do was set:

>   <stream-pipeline 
> class="org.apache.cocoon.components.pipeline.CachingStreamPipeline" 
> pool-max="32" pool-min="16" pool-grow="4" />


>   <event-pipeline 
> class="org.apache.cocoon.components.pipeline.CachingEventPipeline" 
> max="32" pool-min="16" pool-grow="4" />

in my cocoon.xconf file, and:

>    <map:generator  name="file"        
> src="org.apache.cocoon.generation.FileGenerator" label="content" max="32"
>  pool-min="16" pool-grow="4" />


>    <map:transformer     name="xslt"      
> src="org.apache.cocoon.transformation.TraxTransformer" pool-max="32" 
> pool-min="16" pool-grow="4">


>    <map:serializer name="xml"    mime-type="text/xml"         
> src="org.apache.cocoon.serialization.XMLSerializer" pool-max="32" 
> pool-min="16" pool-grow="4"/>

in my sitemap.xmap file.

and this made a big difference.  Last weeks 6.4 secs is down to todays 100 

I'm still a little purplexed as to why every new TraxTransformer was 
creating 8 new JaxpParsers - this still seems like some kind of 
inefficiency to me, but I'll have to leave it be for the moment.


On Wednesday, August 1, 2001, at 11:08  pm, Stuart Roebuck wrote:

> Vadim,
> Thanks,  a much appreciated suggestion - I'll try that tomorrow.
> Stuart.
> On Wednesday, August 1, 2001, at 10:01  pm, Vadim Gritsenko wrote:
>>> know it a lot better than me; if the second then please let me know so
>>> that I know it's worth pursuing.
>>> I do know that something is causing requests for the same page to create
>>> 16 new JaxpParser components on every invocation,
>> Check pool size (add some debug info into
>> .
>> If it's always growing, on every request, up to enormous size, then it's 
>> clear that
>> components are not released properly somewhere. If it's growing and 
>> shrinking - it
>> just means that you need to define bigger pool for this component kind 
>> (xslt in your
>> case).
>> Vadim

Stuart Roebuck                        
Lead Developer                               Java, XML, MacOS X, XP, etc.
ADOLOS                                           <>

To unsubscribe, e-mail:
For additional commands, email:

View raw message