slavaz

Thanks to effingen and having made changes to plugin as advised I was able to compile reports with Java 8. Sorry, can not figure out how to format it nicely, anyway here it is org.codehaus.mojo jasperreports-maven-plugin 1.0-beta-2 ${project.basedir}/src/main/webapp/templates/ ${project.basedir}/src/main/webapp/templates/ compile compile-reports net.sf.jasperreports jasperreports 4.7.0 eclipse jdtcore org.eclipse.jdt.core.compiler ecj 4.4.2 org.codehaus.groovy groovy-all 1.7.5

Hi Teodor, after few experiments I also came to think that something was wrong with the class loading. I do not know where exactly is the problem, is it in orion or is it a feature of orion-jasper combination. For some reasons Jasper is not stable on the WEB-INF/lib level. I've solved the problem by moving Jasper libraries up under orion/lib. For the last three weeks there was not a single glitch. Thanks, Slava.

No, we do not get errors all the time. Jasper works for some time, few hours. Then all of a sudden something happens with it and customers get 'Incompatible value assigned..' error when they try to create a report. If they try to view previously created reports that were saved in the database, they get "500 Internal server error". All the rest of the web application continues to work, iText reports work fine. It's just Jasper component that looses its mind and does not remember its own class hierarchy.

Still no reply, eh? OK, here is another try with different failure scenario. When jasper fails after working for few hours new reports (JasperPrint objects) can not be created because of this "Incompatible value" stuff. But when one tries to view JasperPrint object previously created and stored in the database the server error happens. 500 Internal Server Errorjava.lang.ClassCastException: net.sf.jasperreports.engine.export.DefaultExporterFilterFactory cannot be cast to net.sf.jasperreports.engine.export.ExporterFilterFactory at net.sf.jasperreports.engine.export.ExporterFilterFactoryUtil.getFilterFactory(ExporterFilterFactoryUtil.java:57) at net.sf.jasperreports.engine.JRAbstractExporter.createFilter(JRAbstractExporter.java:1071) at net.sf.jasperreports.engine.export.JRPdfExporter.exportReport(JRPdfExporter.java:237) at net.sf.jasperreports.j2ee.servlets.PdfServlet.service(PdfServlet.java:143) at javax.servlet.http.HttpServlet.service(HttpServlet.java:333) at com.evermind[Orion/2.0.7 (build 11273)]._ha.doFilter(Unknown Source) at Dpnoop.Manifest.puro.reports.PuroReportSelectorFilter.doFilter(PuroReportSelectorFilter.java:76) at com.evermind[Orion/2.0.7 (build 11273)]._csb._pvd(Unknown Source) at com.evermind[Orion/2.0.7 (build 11273)]._csb._boc(Unknown Source) at com.evermind[Orion/2.0.7 (build 11273)]._ax._lsc(Unknown Source) at com.evermind[Orion/2.0.7 (build 11273)]._ax._uab(Unknown Source) at com.evermind[Orion/2.0.7 (build 11273)]._bf.run(Unknown Source) Exception is thrown on the second of two lines of code: Class clazz = JRClassLoader.loadClassForName(factoryClassName); return (ExporterFilterFactory)clazz.newInstance(); Newly created DefaultExporterFilterFactory object can not be cast to the interface it implements? Something wrong with JRClassLoader? Any ideas how to fix it? Thanks. Post Edited by slavaz at 05/01/2009 00:57

Few days and no response? :( Does it mean that nobody else had ever had such problem? We do have Jasper fail every day for no apparent reason. We run Windows Server 2003 Standard x64 Edition. It is Dell PowerEdge 2900 with Xeon processors. I've updated Java from 1.5.0 to 1.6.0u13, VM is Java HotSpot 64-Bit Server VM. It did not help though. Jasper works fine until some time in the afternoon then fails. There is not much load though, just few reports get created during the day. It is very frustrating. May be developers will chime in? Thanks.

Hi all! Is there a solution to the problem described here - http://www.jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=5049#5049 We also run Orion server, version 2.0.6. We have one web application that is accessible by many customers and uses Jasper to create reports. The problem that we have is that Jasper quits to work after some time. When it happens, we get the error Caused by: net.sf.jasperreports.engine.JRException: Incompatible net.sf.jasperreports.engine.data.JRBeanCollectionDataSource value assigned to parameter REPORT_DATA_SOURCE in the CourierPickupSheet dataset. at net.sf.jasperreports.engine.fill.JRFillDataset.setParameter(JRFillDataset.java:881) at net.sf.jasperreports.engine.fill.JRFillDataset.setFillParameterValues(JRFillDataset.java:626) at net.sf.jasperreports.engine.fill.JRFillDataset.setParameterValues(JRFillDataset.java:577) at net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(JRBaseFiller.java:1211) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:842) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:810) at net.sf.jasperreports.engine.fill.JRFiller.fillReport(JRFiller.java:89) at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:601) at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:517) We use Java 1.5.09 and I have recompiled Jasper sources under same Java that we run the server on, just in case. I tried to synchronize call to JasperFillManager on a static object, like this synchronized (oJasperLock) { jasperPrint = JasperFillManager.fillReport(fullpath, params, reportDS); } Synchronization did not help. I've modified JRFillDataset.setParameter() to log class names and here is the result: parameter.getValueClass() = interface net.sf.jasperreports.engine.JRDataSource' value.getClass() = 'class net.sf.jasperreports.engine.data.JRBeanCollectionDataSource' parameter.getValueClass().isInstance(value) = 'false' Looks like Class.isInstance does not work, since JRBeanCollectionDataSource is an implementation of JRDataSource. It should work, but does not! We've only recently started to use Jasper and it really becomes a pain for our customers. Any ideas how this can be cured? Thanks!