I am afraid it won't help. I already increased the heap size to
2,5/3,5g min/max, but I still can't plot any pdf including raster out,
whether the raster is at any size. It seems like something is totally
broken but I can't imagine that a user could get the whole system to
crash. I am printing large images; the FOP manual said: do not use large images. So I don't know is this project of mine sane, but it seemed to be working nice with 12000x12000x24 rasters until I got creedy and add the pixel amount. It crashed and after that, I haven't been able to print out a single raster through FOP. reg mika Kai Mütz kirjoitti: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]Try to increase the memory allocated to the JVM: http://xmlgraphics.apache.org/fop/0.94/running.html#memoryLehtonen, Mika <> wrote:Hi, the new fop worked perfectly till I tried to plot a pdf with a huge raster in it. After that I haven't been able to use it. I get this error even if I restart the Tomacat or boot the whole server. Any idea what is causing this malfunction? reg. mika HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet execution threw an exception root cause java.lang.OutOfMemoryError: PermGen space java.lang.ClassLoader.defineClass1(Native Method) java.lang.ClassLoader.defineClass(ClassLoader.java:620) java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLo ader.java:1817)org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.jav a:872)org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav a:1325)org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav a:1204)java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)org.apache.fop.image.analyser.ImageReaderFactory.<clinit>(ImageReaderFactory .java:57)org.apache.fop.image.ImageFactory.loadImage(ImageFactory.java:220) org.apache.fop.image.ImageLoader.loadImage(ImageLoader.java:56) org.apache.fop.image.ContextImageCache.getImage(ImageFactory.java:432) org.apache.fop.image.ImageFactory.getImage(ImageFactory.java:157) org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:70) org.apache.fop.fo.FObj.processNode(FObj.java:125)org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.jav a:320)org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:185)org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:95)org.apache.xml.serializer.ToXMLSAXHandler.closeStartTag(ToXMLSAXHandler.java :206)org.apache.xml.serializer.ToSAXHandler.flushPending(ToSAXHandler.java:279)org.apache.xml.serializer.ToXMLSAXHandler.endElement(ToXMLSAXHandler.java:24 5)org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 1401)org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2400)org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 1376)org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2400)org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 1376)org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2400)org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 1376)org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2400)org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 1376)org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2400)org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 1376)note The full stack trace of the root cause is available in the Apache Tomcat/6.0.14 logs. Kai Mütz kirjoitti: Lehtonen, Mika <> wrote: Superb! ..but still too complicated for me, I'm afraid. Could you be more specific on compling part? I tried to compile that code with javac (1.6.0_04) and got 73 errors. Then I "stole" the You have to compile it with the cocoon 2.1.11 libs in classpath. This should work. I haven't tried it with java 1.6. You need at least the following libs in classpath: fop.jar; cocoon-2.1.11.jar; avalon-framework-api-4.3.jar; avalon-framework-impl-4.3.jar; avalon-logkit-2.1.jar; excalibur-sourceresolve-2.1.jar; excalibur-xmlutil-2.1.jar; excalibur-pool-api-2.1.jar; commons-lang-2.3.jar Regards, Kai --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] |
- Newer FOP to Cocoon 2.1.11 Lehtonen, Mika
- RE: Newer FOP to Cocoon 2.1.11 Kai Mütz
- Re: Newer FOP to Cocoon 2.1.11 Lehtonen, Mika
- RE: Newer FOP to Cocoon 2.1.11 Kai Mütz
- Re: Newer FOP to Cocoon 2.1.11 Lehtonen, Mika
- Re: Newer FOP to Cocoon 2.1.11 Lehtonen, Mika
- RE: Newer FOP to Cocoon 2.1.11 Kai Mütz
- Re: Newer FOP to Cocoon 2.1.11 Lehtonen, Mika
- RE: Newer FOP to Cocoon 2.1.1... Kai Mütz
- Re: Newer FOP to Cocoon 2.1.1... Joerg Heinicke
- Re: Newer FOP to Cocoon 2.1.1... Lehtonen, Mika
- Re: Newer FOP to Cocoon 2.1.1... Lehtonen, Mika
- Re: Newer FOP to Cocoon 2.1.11 Huib Verweij