bportas

Ploblem solved! Now I know what I was missing. The Virtualizer doesn't help until you set the jasper report properties "isUsingCache" to false and "isLazy" to true. So that's the end of the story (I hope)

Sorry, but this problem is still alive (at least for me). I'm getting "out of memory" while filling out the report, even passing a JRFileVirtualizer to the JasperReport object. Well, I'm printing images the size of about 2MB each. They are not stored in the database, so I think it's not a problem with JRDataSource. Only a reference to the folder and name of the image is provided by the JRDataSource. The message appears after retrieving image number 24, with or without JRVirtualizer (I wonder! Is there some else to do than simply passing the virtualizer as REPORT_VISTUALIZER to the report?) No problems using iReport instead. I'm using jasperreports-3.5.0.jar. There must be something I'm missing and I don't know what! (live's hard indeed) Any ideas out there? Thanks Code:List images = new DocumentoArrollamiento( ).fotosTramo( tramo, ronda );System.out.println( "----------Nro.images = " + images.size( ) );JRFileVirtualizer fileVirtualizer = new JRFileVirtualizer( 3, "c:\\TEMP" );//tried 100 pages too, but didn't workMap _params = new HashMap( );_params.put( JRParameter.REPORT_VIRTUALIZER, fileVirtualizer );File tempFile = File.createTempFile( "jasper_", ".pdf" );JasperReport jasperReport = (JasperReport) JRLoader.loadObject(_jrxmlFileName );System.out.println( "---------->jasperReport loaded" );JasperPrint jasperPrint = JasperFillManager.fillReport(jasperReport, _parametrosInforme, _jasperReport );System.out.println( "---------->I never get here!!" );JasperExportManager.exportReportToPdfFile(jasperPrint,tempFile.getAbsolutePath());...