Deadlock when previewing a report on MacOS X

Changed Status from New to Feedback Requested

Changed Assigned User from - to @User_306070

---

Hi,is it possible to have the JRXML plus additional files attached here?Just in case if you are able to reproduce the issue with a minimal configuration involving the "SampleDB" data adapter it would be better. In this case you will not have to attach any "personal" details regarding the report you are creating.Regards,Massimo.

Changed Assigned User from @User_306070 to @anonymous

---

Hi Massimo,sorry for the wait. Only just now I have found the time to strip the report down. If I import this project in JasperSoft Studio, open the jrxml and click preview, it hangs on the described deadlock.It definitely has something with class loading, because, if I open a small default report before and click on preview on that report and then preview the attached report, it won't hang (I guess because the relevant classes are already loaded and thus the race condition does not occur in that case).Best,Stefan

Changed Status from Feedback Requested to New

---

To provide more information, I have also enabled OSGi class loading tracing (via the Eclipse -debug parameter and an .options file containing org.eclipse.osgi/debug/loader=true).

I have captured the output from the moment I click on preview.

 

If I interpret this correctly, the two classes being loaded when the deadlock occurs are

 

BundleLoader[com.jaspersoft.studio_6.0.1.final].loadBundleClass(net.sf.jasperreports.export.SimpleHtmlReportConfiguration)

BundleLoader[net.sf.jasperreports_6.0.1.final].findLocalClass(net.sf.jasperreports.export.SimpleHtmlReportConfiguration)

 

and

 

BundleLoader[com.jaspersoft.studio_6.0.1.final].loadBundleClass(groovy.runtime.metaclass.Script1MetaClass)

BundleLoader[com.jaspersoft.studio_6.0.1.final].findLocalClass(groovy.runtime.metaclass.Script1MetaClass)

 

Changed Status from New to Assigned

Changed Assigned User from @anonymous to @mrabbi

---

Hi, I'm currently working on the issue. I was able to solve the problem modifying the target platform and plugin dependencies, basically moving out the groovy jar from the net.sf.jasperreports plug-in and using it as an OSGI bundle.Anyhow since I'm trying to investigate similar steps for other jars, I will let you know when an integration build is ready.Regards,Massimo.

Changed Resolution from Open to Fixed

Changed Status from Assigned to Resolved

---

Hi Stefan,just to let you know that by the end of the day I will publish a newer integration build of JSS. You will be able to pick-it from here: https://sourceforge.net/projects/jasperstudio/files/beta-release/As mentioned in my previous comment, it appears that moving the groovy-all jar to be used directly as an OSGI bundle for the target platform solved the problem.The problem should be gone, at least now in my development environment it does. I'm no longer able to reproduce the hang on JSS like I was before.Regards,Massimo.