You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Davor Cengija <da...@mail.inet.hr> on 2002/11/04 16:34:53 UTC
OutOfMemoryError on Websphere, not in WSAD test environment
We're creating some on the fly pdf files in WebSphere Application Developer
(WSAD 4.0.3) and testing it in its internal WebSphere Test Environment.
Everything works just fine, and PDF files are created and displayed. BTW,
its nothing too complicated, usualy single page with single table in it.
However, on our real WebSphere Application Server v4.0.4, I'm getting the
following error:
[11/4/02 16:05:59:024 CST] 1cb7b002 WebGroup X Servlet Error: :
java.lang.OutOfMemoryError
at org.apache.fop.fonts.FontFileReader.init(FontFileReader.java:35)
at
org.apache.fop.fonts.FontFileReader.<init>(FontFileReader.java:68)
at
org.apache.fop.render.pdf.fonts.MultiByteFont.getFontFile(MultiByteFont.java
:197)
at
org.apache.fop.render.pdf.fonts.LazyFont.getFontFile(LazyFont.java:173)
at
org.apache.fop.pdf.PDFDocument.makeFontDescriptor(PDFDocument.java:898)
at org.apache.fop.pdf.PDFDocument.makeFont(PDFDocument.java:799)
at
org.apache.fop.render.pdf.FontSetup.addToResources(FontSetup.java:206)
at
org.apache.fop.render.pdf.PDFRenderer.stopRenderer(PDFRenderer.java:157)
at
org.apache.fop.apps.StreamRenderer.stopRenderer(StreamRenderer.java:144)
at
org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:205)
at
org.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1230)
at
org.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidato
r.java:1146)
at
org.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch
(XMLDocumentScanner.java:1499)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at org.apache.fop.apps.Driver.render(Driver.java:481)
at org.apache.fop.apps.Driver.run(Driver.java:554)
at
hr.noveteh.hgk.tdozvole.web.struts.PrintActionTemplate.createPdf(PrintAction
Template.java:95)
at
hr.noveteh.hgk.tdozvole.web.struts.actions.prijevoznik.predracun.PredracunPr
intAction.executeSpecific(PredracunPrintAction.java:75)
at
hr.noveteh.hgk.tdozvole.web.struts.TransportneDozvoleActionTemplate.execute(
TransportneDozvoleActionTemplate.java:56)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProces
sor.java:437)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:452)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:297)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Co
mpiled Code))
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Co
mpiled Code))
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:239)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:151)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:315)
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va:60)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Comp
iled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled
Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)
Does it really means that WAS needs more memory or it is maybe some
recursion gone mad :-) or maybe broken font file (we're using TTF's).
Development is on windows machines and deployment on AIX.
Thanks,
Davor
Re: OutOfMemoryError on Websphere, not in WSAD test environment
Posted by Davor Cengija <da...@mail.inet.hr>.
"J.Pietschmann" <j3...@yahoo.de> wrote in message
news:3DC82C9F.80609@yahoo.de...
> Davor Cengija wrote:
> > I'll try different fonts and FOP versions and let you know what happens.
>
> Check the memory settings of your JVM first. The Unix version
> may have a smaller default, or things just take up more space
> there (caching, threadss, whatever), or you are even using a
> completely different JVM version.
> Consult your friendly WebSphere manual about where to set
> addidional JVM flags.
Might be, since I got the following error, also OutOfMemoryError:
[11/5/02 18:07:09:215 CST] 51d691ea WebGroup X Servlet Error: :
java.lang.OutOfMemoryError
at
org.apache.fop.fonts.TTFSubSetFile.readFont(TTFSubSetFile.java:584)
at
org.apache.fop.render.pdf.fonts.MultiByteFont.getFontFile(MultiByteFont.java
:200)
at
org.apache.fop.render.pdf.fonts.LazyFont.getFontFile(LazyFont.java:173)
at
org.apache.fop.pdf.PDFDocument.makeFontDescriptor(PDFDocument.java:898)
at org.apache.fop.pdf.PDFDocument.makeFont(PDFDocument.java:799)
at
org.apache.fop.render.pdf.FontSetup.addToResources(FontSetup.java:206)
at
org.apache.fop.render.pdf.PDFRenderer.stopRenderer(PDFRenderer.java:157)
at
org.apache.fop.apps.StreamRenderer.stopRenderer(StreamRenderer.java:144)
at
org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:205)
at
org.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1230)
at
org.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidato
r.java:1146)
at
org.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch
(XMLDocumentScanner.java:1499)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at org.apache.fop.apps.Driver.render(Driver.java:481)
at org.apache.fop.apps.Driver.run(Driver.java:554)
at
hr.noveteh.hgk.uvozizvoz.web.struts.PrintActionTemplate.createPdf(PrintActio
nTemplate.java:102)
at
hr.noveteh.hgk.uvozizvoz.web.struts.actions.export.ExportPDFAction.executeSp
ecific(ExportPDFAction.java:57)
at
hr.noveteh.hgk.uvozizvoz.web.struts.UvozIzvozActionTemplate.execute(UvozIzvo
zActionTemplate.java:51)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProces
sor.java:437)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at
org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled
Code))
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Co
mpiled Code))
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java(Co
mpiled Code))
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java(Compiled Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java(Compil
ed Code))
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java(Compiled Code))
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java(Compiled Code))
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java(Compiled Code))
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java(Compiled Code))
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va(Compiled Code))
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Comp
iled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled
Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)
Thanks for the tips, I'll let you know what's going on.
Re: OutOfMemoryError on Websphere, not in WSAD test environment
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Davor Cengija wrote:
> I'll try different fonts and FOP versions and let you know what happens.
Check the memory settings of your JVM first. The Unix version
may have a smaller default, or things just take up more space
there (caching, threadss, whatever), or you are even using a
completely different JVM version.
Consult your friendly WebSphere manual about where to set
addidional JVM flags.
J.Pietschmann
Re: OutOfMemoryError on Websphere, not in WSAD test environment
Posted by Davor Cengija <da...@mail.inet.hr>.
"Oleg Tkachenko" <ol...@multiconn.com> wrote in message
news:3DC6CC81.9050100@multiconn.com...
> Davor Cengija wrote:
> > We're creating some on the fly pdf files in WebSphere Application
Developer
> > (WSAD 4.0.3) and testing it in its internal WebSphere Test Environment.
> > Everything works just fine, and PDF files are created and displayed.
BTW,
> > its nothing too complicated, usualy single page with single table in it.
> >
> > However, on our real WebSphere Application Server v4.0.4, I'm getting
the
> > following error:
> >
> > [11/4/02 16:05:59:024 CST] 1cb7b002 WebGroup X Servlet Error: :
> > java.lang.OutOfMemoryError
> > at
org.apache.fop.fonts.FontFileReader.init(FontFileReader.java:35)
> That allocates byte array for reading font file. Which fonts are you
using?
>
I'm using TTF files from Windows 2000, namelly Arial (all combinations of
slants and weights) and Lucida. Everything is fine on Windows, but on AIX
the error mentioned before appears.
FOP is 0.20.3.
I'll try different fonts and FOP versions and let you know what happens.
Thanks.
Re: OutOfMemoryError on Websphere, not in WSAD test environment
Posted by Oleg Tkachenko <ol...@multiconn.com>.
Davor Cengija wrote:
> We're creating some on the fly pdf files in WebSphere Application Developer
> (WSAD 4.0.3) and testing it in its internal WebSphere Test Environment.
> Everything works just fine, and PDF files are created and displayed. BTW,
> its nothing too complicated, usualy single page with single table in it.
>
> However, on our real WebSphere Application Server v4.0.4, I'm getting the
> following error:
>
> [11/4/02 16:05:59:024 CST] 1cb7b002 WebGroup X Servlet Error: :
> java.lang.OutOfMemoryError
> at org.apache.fop.fonts.FontFileReader.init(FontFileReader.java:35)
That allocates byte array for reading font file. Which fonts are you using?
--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel