Xarnius

I'm also encountering these errors. Code:DEBUG [Nov 03 2011 08:36:42 AM - AbstractBeanFactory] (getTypeForFactoryBean) - Ignoring bean creation exception on FactoryBean type checkorg.springframework.beans.factory.BeanCreationException: Error creating bean with name 'titleBaseFontSize': Invocation of init method failed; nested exception is java.lang.NoSuchFieldException: TITLE_BASEFONT_SIZE

Hi sumadha, It appears you are running into a similar issue, but different enough to merit its own thread. Also when "dumping" large amounts of code it is cleaner to use the code box. Would you be ok with moving your topic to its own thread dealing with AWT images, and remove your post from this thread? Thanks in advance. I saw you asked how to create a new topic in a previous thread. From the Main topics page, you may click new topic to do this.

frankhassanabad Wrote: This might be a library limitation. Thanks for the stack trace. Are you running on a 32 bit or 64 bit JVM and what are *all* of your memory settings for that? Post Edited by frankhassanabad at 11/02/2011 16:04 JVM 32 bitThe weblogic console shows: -Xms2048m -Xmx2048m -XX:MaxPermSize=256m

You caught up with him now :)

I am in the process of getting that information for you. However, I do find it interesting that it is only when the 508 tags are turned on that there is an issue. There must be some connection between the 508 tags and the call to the iText columnText.go method that is handled differently between these two scenarios (508 tags on/off).

Here is the stacktrace of the exception: Code:Oct 20, 2011 2:33:24 PM com.caucho.hessian.server.HessianSkeleton invokeWARNING: java.lang.OutOfMemoryError: Java heap spacejava.lang.OutOfMemoryError: Java heap space at com.lowagie.text.pdf.BidiLine.<init>(Unknown Source) at com.lowagie.text.pdf.ColumnText.addWaitingPhrase(Unknown Source) at com.lowagie.text.pdf.ColumnText.go(Unknown Source) at com.lowagie.text.pdf.ColumnText.go(Unknown Source) at net.sf.jasperreports.engine.export.JRPdfExporter.exportText(JRPdfExporter.java:2108) at net.sf.jasperreports.engine.export.JRPdfExporter.exportElements(JRPdfExporter.java:735) at net.sf.jasperreports.engine.export.JRPdfExporter.exportPage(JRPdfExporter.java:695) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReportToStream(JRPdfExporter.java:584) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:380) at net.sf.jasperreports.engine.JasperExportManager.exportReportToPdfFile(JasperExportManager.java:130) at org.ifmc.report.engine.Jasper370Service.runReport(Jasper370Service.java:244) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.caucho.hessian.server.HessianSkeleton.invoke(HessianSkeleton.java:157) at com.caucho.hessian.server.HessianServlet.service(HessianServlet.java:365) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)Exception in thread "Timer-5" java.lang.OutOfMemoryError: Java heap space at com.lowagie.text.pdf.BidiLine.<init>(Unknown Source) at com.lowagie.text.pdf.ColumnText.addWaitingPhrase(Unknown Source) at com.lowagie.text.pdf.ColumnText.go(Unknown Source) at com.lowagie.text.pdf.ColumnText.go(Unknown Source) at net.sf.jasperreports.engine.export.JRPdfExporter.exportText(JRPdfExporter.java:2108) at net.sf.jasperreports.engine.export.JRPdfExporter.exportElements(JRPdfExporter.java:735) at net.sf.jasperreports.engine.export.JRPdfExporter.exportPage(JRPdfExporter.java:695) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReportToStream(JRPdfExporter.java:584) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:380) at net.sf.jasperreports.engine.JasperExportManager.exportReportToPdfFile(JasperExportManager.java:130) at org.ifmc.report.engine.Jasper370Service.runReport(Jasper370Service.java:244) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.caucho.hessian.server.HessianSkeleton.invoke(HessianSkeleton.java:157) at com.caucho.hessian.server.HessianServlet.service(HessianServlet.java:365) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

I started a new topic not very many days ago related to this same thing, and have had some views, but no responses. Any help would be appreciated.. I have tried using Jasper versions 3.7.0, 4.1.2, and the most recently released 4.1.3 and am still receiving an OutOfMemory exception when PDF 508 tags are turned on. When they are off the report completes successfully. Thanks

Hello, I have been tasked with producing a Proof of Concept surrounding the ability to produce extremely large reports. We have been using the Jasper engine within an in-house reporting system coupled with iReports, since version .0.6.4. We have recently been asked by our clients to enhance the reporting engine to run reports that would easily exceed 1GB in size in PDF format. I'm currently using version 3.7.0 of the Jasper engine and has the following code snippets generating the report. I'm able to generate a report in PDF I have the compression tag set within the exportReportToPdfFile, and use the virtualizer. However, when I add the following tags to turn on the 508 PDF tags, the swap file finishes successfully, but at 75-90 MB during the PDF generation I take an OutOfMemory exception. I have exhausted nearly every alternative I can think of, but know that the problem is somehow tied to the actual PDF generation piece, the fillReport is completing and greating a 3.7GB swap file. The largest report I was able to run, without tags turned on was 1.15GB, took 9 hrs to run, with a total of 623,057 pages, but when I turned the tags on it didn't complete. Is it trying to create the PDF file in memory only? I have tried dropping Jasperreports' 4.1.2 iText library into the 3.7.0 Jasper engine, version 2.1.7, but the same error occurs. This doesn't appear to be an issue related to the virtualizer, however, do the above parameters for the swapFile and invoking the virtualizer look practical? Any assistance would greatly appreciated. -Dan Code:JRSwapFile swapFile = new JRSwapFile(tempdir, 4096 , 4096);System.out.println("Initializing report virtualizer");virtualizer = new JRSwapFileVirtualizer(300, swapFile, true);parameters.put(JRParameter.REPORT_VIRTUALIZER, virtualizer);System.out.println("parameters: " + parameters);System.out.println("virtualizer parameter set - starting pdf creation");long start = System.currentTimeMillis();System.out.println("fillreport file name: " + qc.getAppProperty("ReportDir") + "/" + rpt);JasperPrint jasperPrint = JasperFillManager.fillReport(qc.getAppProperty("ReportDir") + "/" + rpt, parameters, conn);System.out.println("fillreport time : " + (System.currentTimeMillis() - start)); start = System.currentTimeMillis();System.out.println("beginning PDF export");JasperExportManager.exportReportToPdfFile(jasperPrint, tempdir + "/" + qr.queID + "." + ext);System.out.println("PDF creation time : " + (System.currentTimeMillis() - start));///////////////////////////// exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint); exporter.setParameter(JRPdfExporterParameter.IS_TAGGED, Boolean.TRUE); exporter.setParameter(JRPdfExporterParameter.IS_COMPRESSED, Boolean.TRUE); exporter.setParameter(JRPdfExporterParameter.FORCE_SVG_SHAPES, Boolean.TRUE); exporter.setParameter(JRPdfExporterParameter.TAG_LANGUAGE, "English-US"); exporter.setParameter(JRExporterParameter.OUTPUT_FILE_NAME, destFileName);

I'm using iReport 3.1.4 and am able to produce 508 Compliant reports locally through IReport, but when I run them through Jasper on our application server, the tags get stripped. Is there some configuration step I'm missing on the Jasper side? Thanks, Dan

The following example report may prove useful as a starting point.

Hello all, I really hope someone has had some experience with this, because I've tried about everything possible I can think of. The problem is this. When I start a table in the page header and row start and close the row and table in the page footer, and make a frame on my detail with a table row on it, and tag the individual details columns with detail tags everything works peachy. I end up with something like this: <table><tr> <tr><td><td><td></tr> </tr></table> Here's where it gets complicated. Say within that main page header/footer table and header/footer row, I have a group which I also want in a table. My first inclination was to put a table start as this had worked within the page header, but this time put it in the group header, and close it in the group footer. Apparently iReport/jasper does not like this at all and won't even generate a PDF. So in table structure this is what I was trying to accomplish. page header -<table><tr> group header 1- <table> detail - <tr><td><td><td></tr> detail - <tr><td><td><td></tr> group footer 1 - </table> page footer -</tr></table> Any assistance would be greatly appreciated!