Cocoon user discussion

Volker Renneberg | 1 Aug 2002 11:42

Resource Reader, broken pipe, large files

Hi!

I've a problem with cocoon 2.0.3 (cataline 4.0.1). The resource reader (or 
catalina?!) seems not to be able to cope with large files. In my current case 
it stops downloading after 2105344 Bytes. I had this problem earlier but 
there around 16 MB.

The log mentions a broken pipe-problem(long but complete, see below). Is there 
any solution to this problem or does anybody now why this happens?

ciao
Volker

-------------------------> Log
FATAL_E (2002-08-01) 10:35.37:728   [core.xslt-processor] 
(/cocoon/pfiles/Shared/madonna/Madonna_-_What_It_Feels_Like_For_A_Girl.mp3) 
HttpProcessor[8080][1]/TraxErrorHandler: Error in TraxTransformer: 
javax.xml.transform.TransformerException: java.io.IOException: Broken pipe
javax.xml.transform.TransformerException: java.io.IOException: Broken pipe
        at 
org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:725)
        at 
org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:422)
        at 
org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:226)
        at 
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2243)
        at 
org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2069)
        at

(Continue reading)

headers

Volker Renneberg | 6 Aug 2002 11:38

Re: Resource Reader, broken pipe, large files

Hi!

I found the problem. I still used the CachingStreamPipeline in cocoon.xconf. 
After substituting this by NonCachingStreamPipeline everything worked fine. 
Unfortunately the reader stuff will not be cached anymore. But with this 
configuration downloads are much faster than before.

Still I've a question about this. In cocoon 2.0.3 in the update notes it's 
been said that stream and pipelines components have to be moved into the 
sitemap (and removed from cocoon.xconf). But it's confusing that both parts 
are still in the cocoon.xconf-2.0.3-file. And there is just an example for 
the "pipelines" on how to move them into the sitemap.xmap, none for the 
"streams"

<map:pipelines default="caching">
     <map:pipeline name="caching" 
src="org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline"/>
     <map:pipeline name="noncaching" 
src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline"/>
  </map:pipelines>

And finally this must not work because there is no such class 
"org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline" in 
the sources of cocoon 2.0.3. So how do I have to understand this update note 
or where do I have to put the information about Caching and NonCaching 
streams/pipelines. And how do I select those stream-components for readers?

ciao
Volker

(Continue reading)

headers

Carsten Ziegeler | 6 Aug 2002 11:48

RE: Resource Reader, broken pipe, large files

The updating document you are refering to is not meant for Cocoon 2.0.3.
It explains updating from 2.0.x to the latest (alpha) version of
Cocoon 2.1-dev which is only available from CVS

Carsten

> -----Original Message-----
> From: Volker Renneberg [mailto:volker.renneberg <at> UniBw-Muenchen.de]
> Sent: Tuesday, August 06, 2002 11:39 AM
> To: cocoon-users <at> xml.apache.org
> Subject: Re: Resource Reader, broken pipe, large files
>
>
> Hi!
>
> I found the problem. I still used the CachingStreamPipeline in
> cocoon.xconf.
> After substituting this by NonCachingStreamPipeline everything
> worked fine.
> Unfortunately the reader stuff will not be cached anymore. But with this
> configuration downloads are much faster than before.
>
> Still I've a question about this. In cocoon 2.0.3 in the update
> notes it's
> been said that stream and pipelines components have to be moved into the
> sitemap (and removed from cocoon.xconf). But it's confusing that
> both parts
> are still in the cocoon.xconf-2.0.3-file. And there is just an
> example for
> the "pipelines" on how to move them into the sitemap.xmap, none for the

(Continue reading)

headers

Vadim Gritsenko | 1 Aug 2002 14:46

RE: Resource Reader, broken pipe, large files

> From: Volker Renneberg [mailto:volker.renneberg <at> UniBw-Muenchen.de]
> 
> Hi!
> 
> I've a problem with cocoon 2.0.3 (cataline 4.0.1). The resource reader
(or
> catalina?!) seems not to be able to cope with large files. In my
current case
> it stops downloading after 2105344 Bytes. I had this problem earlier
but
> there around 16 MB.
> 
> The log mentions a broken pipe-problem(long but complete, see below).
Is there
> any solution to this problem or does anybody now why this happens?

Stack trace points to XSLT transformation, but your question is about
reader. I think that this stacktrace is not correlated to the issue you
are experiencing.

PS No, I've not seen issues with large files (did not have large files
in my app). BTW, it is known that plain web server will give better
performance on static and/or large files.

Vadim

> ciao
> Volker
> 
> -------------------------> Log

(Continue reading)