wooderi

No, I ended up having to switch to barcode4j instead of using barbecue.

From what we were told by IBM, it should be fixed in OS version AIX 5.3 TL12, Service Pack 2 released in December. But we haven't had a chance to upgrade yet. I'm still using the work around JAVA_COMPILER=NONE (Slow!!)

Any ideas for a workaround to this problem without removeing swapfile or changeing barcode formats? When createing reports using 128c with barbecue and JRSwapFileVirtualizer set, it works fine unless the page count goes over the swapfile page size... Code:JRSwapFileVirtualizer virtualizer = null;virtualizer = new JRSwapFileVirtualizer(20, new JRSwapFile("/tmp",2048, 1024), true);jasperParameter.put(JRParameter.REPORT_VIRTUALIZER, virtualizer);When it hits page 21 of the report it throws...net.sf.jasperreports.engine.JRRuntimeException: java.io.NotSerializableException: net.sourceforge.barbecue.linear.code128.CharBuffer at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer.writeData(JRAbstractLRUVirtualizer.java:578) at net.sf.jasperreports.engine.fill.JRSwapFileVirtualizer.pageOut(JRSwapFileVirtualizer.java:88) at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer.virtualizeData(JRAbstractLRUVirtualizer.java:531) at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer$Cache$LRUScanMap.processRemovedLRU(JRAbstractLRUVirtualizer.java:135) at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer$Cache$LRUScanMap.removeLRU(JRAbstractLRUVirtualizer.java:121) at org.apache.commons.collections.LRUMap.put(LRUMap.java:122) at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer$Cache.put(JRAbstractLRUVirtualizer.java:196) at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer.requestData(JRAbstractLRUVirtualizer.java:501) at net.sf.jasperreports.engine.base.JRVirtualPrintPage.ensureVirtualData(JRVirtualPrintPage.java:319) at net.sf.jasperreports.engine.base.JRVirtualPrintPage.getElements(JRVirtualPrintPage.java:311) at net.sf.jasperreports.engine.export.JRPdfExporter.exportPage(JRPdfExporter.java:694) 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:122) at runreport.ProcessReport.Process(ProcessReport.java:133) at runreport.doComms.run(SocketServer.java:164) at java.lang.Thread.run(Thread.java:736)Caused by: java.io.NotSerializableException: net.sourceforge.barbecue.linear.code128.CharBuffer at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1165) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1401) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1401) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1401) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:332) at java.util.ArrayList.writeObject(ArrayList.java:706) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:957) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1470) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1401) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1401) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:332) at java.util.ArrayList.writeObject(ArrayList.java:706) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:957) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1470) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1401) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:332) at net.sf.jasperreports.engine.fill.JRAbstractLRUVirtualizer.writeData(JRAbstractLRUVirtualizer.java:572) ... 16 more

Thanks for the update! Hope it solves the issue. Does the IBM update have reference number or name so we can request the same patch be installed?

I found a workaround for this by turning off the JIT compiler. export JAVA_COMPILER=NONE or -Djava.compiler=NONE but processing time on large reports are much much slower. Please let us know if you find anything out from IBM.

Has anyone seen this issue (Unhandled exception Type=Segmentation error vmState=0x0005ff0c)? We are running jasper reports 3.7.1 on AIX 5.3 with Java6 and iText-2.1.0. The report uses XML datasource and from time to time we are getting intermittent core dumps with error... Unhandled exception Type=Segmentation error vmState=0x0005ff0c Method_being_compiled=com/lowagie/text/pdf/PdfDocument.writeLineToContent(Lcom/l owagie/text/pdf/PdfLine;Lcom/lowagie/text/pdf/PdfContentByte;Lcom/lowagie/text/p df/PdfContentByte;[Ljava/lang/Object;F)V I can reprocess the same report / XML file 100+ times after getting this error without it happening again. Then after awhile it does it again. Any ideas what might be causing this, or is it possible to catch the exception to avoid the JVM crashing? Thanks in advance! Code: JRDataSource xmlcon = xmlConnection(datafile, selectstatement); jPrint = JasperFillManager.fillReport(jasperReport, jasperParameter, xmlcon); JasperExportManager.exportReportToPdfFile(jPrint, outputfile + ".pdf"); public JRDataSource xmlConnection(String datafile, String selectstatement) { JRDataSource connection = null; try { JRDataSource ds = new JRXmlDataSource(datafile, selectstatement); connection = ds;