I have a question regarding Cocoon profiling. In the cocoon.log, I see
that each request is timed. However, nowhere in my Cocoon configuration
do I see profiling enabled. Is it because I have the profiling block
compiled into Cocoon? How can I disable this profiling?
INFO (2008-07-29) 15:39.10:205 [access] (/cocoon/myapp/login.html)
http-192.168.0.1-80-1/CocoonServlet: 'across/login.html' Processed by
Apache Cocoon 2.1.11 in 39 milliseconds
sitemap.xmap:
<map:pipes default="caching">
<map:pipe name="caching" pool-max="${caching-pipeline.pool-max}"
src="org.apache.cocoon.components.pipeline.impl.CachingProcess
ingPipeline">
<!--+
| If not specified, the value of the outputBufferSize
parameter is -1.
| This will cause Cocoon to buffer all output until
processing has finished
| before sending it to the client. This has the advantage
that in case
| an error occurs during the processing of the SAX-pipeline,
Cocoon is still
| able to reset the response and send an error page instead.
Otherwise the
| error page will be appended to the output already send to
the client.
| If you are generating larger pages, it might be beneficial
to enable
| this parameter, so that output is gradually send to the
client as it
| is being generated.
| For more granularity, you can also supply this parameter to
| individual map:pipeline elements (using map:parameter syntax).
+-->
<parameter name="outputBufferSize" value="65536"/>
</map:pipe>
<map:pipe name="caching-point"
pool-max="${caching-point-pipeline.pool-max"
src="org.apache.cocoon.components.pipeline.impl.Cac
hingPointProcessingPipeline">
<!-- parameter name="autoCachingPoint" value="On"/ -->
<!-- parameter name="outputBufferSize" value="8192"/ -->
</map:pipe>
<map:pipe name="noncaching"
pool-max="${noncaching-pipeline.pool-max}"
src="org.apache.cocoon.components.pipeline.impl.NonCachi
ngProcessingPipeline">
<!-- The output buffersize is not related to caching but to the
output. It is important to set it. -->
<parameter name="outputBufferSize" value="65536"/>
</map:pipe>
<!--+
| This pipeline implementation caches the complete content for
a defined
| period of time (expires). The cache key is the current uri.
+-->
<map:pipe name="expires" pool-max="${expires-pipeline.pool-max}"
src="org.apache.cocoon.components.pipeline.impl.ExpiresCaching
ProcessingPipeline">
<parameter name="cache-expires"
value="${expires-pipeline.cache-expires}"/> <!-- Expires in secondes -->
</map:pipe>
<!-- The following two can be used for profiling:-->
<map:pipe name="profile-caching"
src="org.apache.cocoon.components.profiler.ProfilingCachingProcessingPipeline"/>
<map:pipe name="profile-noncaching"
src="org.apache.cocoon.components.profiler.ProfilingNonCachingProcessingPipeline"/>
</map:pipes>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
