Re: Problems serving pdf files

2002-04-20 Thread Erwin

On Fri, 19 Apr 2002, Mike Dewar wrote:

 Thanks but I don't think that I'm using FOP.  All I'm doing is trying to
 serve an existing pdf file:
   map:pipeline
 map:match pattern=foo/**.pdf
   map:read mime-type=application/pdf src=foo/{1}.pdf/
 /map:match
   /map:pipeline

 As an experiment I changed the mime type to text/plain and got the same
 result.

 Mike.

I have had the same problem once serving jpeg files. They were truncated
at 8192 byes, no matter what jpeg file I tried. On the other hand, there
were no problems with gif files (bigger than 8kb).

I solved this by stopping Tomcat/Cocoon, cleaning the Tomcat work
directory and restarting Tomcat/Cocoon. Magic? Some randomly occurring
bug (since I am not the only one having had this problem)?

I hope this solution solves this problem, only one way to find out.

Erwin.


-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Problems serving pdf files

2002-04-19 Thread Mike Dewar

Thanks but I don't think that I'm using FOP.  All I'm doing is trying to
serve an existing pdf file:
  map:pipeline
map:match pattern=foo/**.pdf
  map:read mime-type=application/pdf src=foo/{1}.pdf/
/map:match
  /map:pipeline

As an experiment I changed the mime type to text/plain and got the same
result.

Mike.

On Thu, Apr 18, 2002 at 09:58:49PM +0200, J.Pietschmann wrote:
 Mike Dewar wrote:
  Thanks for this suggestion, but I'm afraid it isn't the answer.  When I
  say larger PDF files I mean over 150K, which is hardly huge.  I tried
  setting the maximum java heap size to 100Mb anyway but it still didn't
  work.
 
 Cocoon uses FOP for rendering PDF, and it can really
 gobble up unbelievable amounts of memory, even for
 relatively small output. 500MB had been reported. It's
 all depending on the complexity of the layout, size of
 embedded graphics and so on. Check your logs, or try to
 generate your PDF with the FOP command line tool. This
 way you can spot FOP problems easier, and if the memory
 shortge is the problem, you can experiment with memory
 settings.
 
 J.Pietschmann
 
 
 -
 Please check that your question has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faqs.html
 
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 _
 This message has been checked for all known viruses by Star Internet
 delivered through the MessageLabs Virus Scanning Service. For further
 information visit http://www.star.net.uk/stats.asp or alternatively call
 Star Internet for details on the Virus Scanning Service.

_
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Problems serving pdf files

2002-04-18 Thread J.Pietschmann

Mike Dewar wrote:
 Thanks for this suggestion, but I'm afraid it isn't the answer.  When I
 say larger PDF files I mean over 150K, which is hardly huge.  I tried
 setting the maximum java heap size to 100Mb anyway but it still didn't
 work.

Cocoon uses FOP for rendering PDF, and it can really
gobble up unbelievable amounts of memory, even for
relatively small output. 500MB had been reported. It's
all depending on the complexity of the layout, size of
embedded graphics and so on. Check your logs, or try to
generate your PDF with the FOP command line tool. This
way you can spot FOP problems easier, and if the memory
shortge is the problem, you can experiment with memory
settings.

J.Pietschmann


-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Problems serving pdf files

2002-04-15 Thread Mike Dewar

I've just installed cocoon 2.0.2 under tomcat 3.3.1 on Redhat Linux.  I
am trying to serve pdf files with the following pipeline added to the
standard sitemap.xmap that came with the (binary) distribution:

  map:pipeline
map:match pattern=foo/**.pdf
  map:read mime-type=application/pdf src=foo/{1}.pdf/
/map:match
  /map:pipeline

For small files this works fine, but larger pdf files get truncated to
122880 bytes.  Can anybody tell me what I'm doing wrong and suggest a
fix?

Thanks, Mike. 

_
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Problems serving pdf files

2002-04-15 Thread Erwin

On Mon, 15 Apr 2002, Mike Dewar wrote:

 For small files this works fine, but larger pdf files get truncated to
 122880 bytes.  Can anybody tell me what I'm doing wrong and suggest a
 fix?

My guess is that java then takes up the maximum allowed heapsize. If you
check to logs, you will probably find java.lang.OutOfMemoryError's.

You will have to make some changes to your startup-files to increase the
maximum allowed heapspace. IIRC you have to use the -Xmxsize option. You
can get a list of these extended options by executing 'java -X' (without
the quotes).

Hope this helps.


-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]