mcauleyt

To help others we have a work around currently but still believe that the Jasper code is doing something it shouldn't really be doing. The work around for an Oracle 10G app server is to use the underlying database connection, rather then the pooled, container controller connection. It's not an ideal solution as we loose some control but it does work. Use the following line: Connection conn1 = ((oracle.jdbc.OracleConnection)conn)._getPC(); Remember not to close conn1 (the real JDBC connection) at the end, rather close conn (the container controlled connection, where close() will just return it to the pool for future reuse). If anyone has a neater solution, I'd be happy to hear it. Thanks, Tim

Hi, We have recently upgraded to Oracle 10g from 9i and Jasper Reports has stopped working. I am trying to run a report, which has sub-reports, from inside the application server and am getting the following error: net.sf.jasperreports.engine.JRException: Unable to get next record. This is caused by : java.sql.SQLException: Closed Statement: next I am calling Jasper using: JasperFillManager.fillReport(reportName, parameterMap, connection); The error is probably being caused by the Oracle 10g JDBC being refined to be more compliant and hence now picking up a potential error that it let go through before. Does anyone have any suggestions? Possibly an alternative to using JasperFillManager.fillReport? Many thanks, Tim

Thanks for that reply. I guessed as much but it's nice to get clarification. Will have to work with a workaround for the time being. Thanks, Tim

Hi, This seems to have been discussed before but I thought I'd ask the question once more and see if there are any updates? Is it possible to combine a jasper report and its sub-reports into a single .jrxml file? The reason I want to do this is that we do not retrieve the jasper report from the file system but pass it into the JasperReports code as an inputstream. One post by Peter Henderson describes combining the compiled subreports (.jasper files) into one large byte[]. This could be a possibility for us but seems extremely hacky. I would have though Japser should be able to handle embedded subreports in the XML file that contain the full report, not just a link to the next jrxml file. Any thoughts are very welcome. Many thanks, Tim