cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Knecht <fel...@apache.org>
Subject Re: [#COCOON-2168] ResourceReader produces Java Heap Overflow when reading a huge resource - ASF JIRA
Date Tue, 11 Mar 2008 10:10:20 GMT

> You need to turn off the buffering of the pipeline as well. I don't 
> have the parameter name at hand, I assume it's "buffer-size" as well 
> but could be different:
>
>     <map:pipeline id="test-nocache" type="noncaching">
>       <map:parameter name="buffer-size" value="0" />
>       <map:match pattern="nocache">
>         <map:read src="/home/felix/tmp/livecd-i686-installer-2007.0.iso"
>           <map:parameter name="buffer-size" value="8192" />
>         </map:read>
>       </map:match>
>     </map:pipeline>
>
> This is usually the way I would define reader pipelines. If the above 
> still produces an OOMError than we have a bug :)
Thanks Carsten, it works. Parameter is "outputBufferSize"

    <map:pipeline id="test-nocache" type="noncaching">
      <map:parameter name="outputBufferSize" value="0" />
      <map:match pattern="nocache">
        <map:read src="/home/felix/tmp/livecd-i686-installer-2007.0.iso" >
          <map:parameter name="buffer-size" value="8192" />
        </map:read>
      </map:match>
    </map:pipeline>


I may ask at this point if the general configuration of noncaching 
pipelines is correct 
(cocoon-core/cocoon-core/src/main/resources/META-INF/cocoon/avalon/cocoon-core-sitemapcomponents.xconf):
    <map:pipe name="noncaching" 
src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline">
      <!-- parameter name="outputBufferSize" value="8192"/ -->
    </map:pipe>

==> As no parameter is specified '-1' is used what in fact leads to the 
same configuration as for caching pipelines?!

Felix


Mime
View raw message