torrana

Changed Priority from Normal to High This is still an issue in version 6.1 of jasper reports. I've attached a proposed fix also, only differences from etdube's fix is to synchronize methods that operate on these ReferenceMaps

Hello, I've seen the same behavoir and have been trying to resolve for some time now. Others have been reporting this also All of my profiling highlights the biggest dominators as the Extensions.ExtensionEnvironment class and it's references to SpringExtensionRegistry, through the use of Hard References in its implementation of apache's Reference Map. This is easily reproducible. I have a couple of reports that are executed over and over. Using your favourite profiler, do a memory profile and you'll clearly see the problem. This has been reported way back to version 4x Hope someone can help out here, in an enterprise environment where systems must be resilient this will never fly.

Changed Severity from Minor to Critical This is critical in mind. With longer running servers my heap of 1 gig will run out in no time. Confirmed the issue is still in 5.0.1Is a patch for this possible?

Hello, I have seen this reported here where on compiling a report generates this warning message. http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=60263 I get this message at runtime and trying to figure out exactly what it means and what is causing it. We're using jasper reports version 4.0.2. That post refers to the javaflow, once removed, the warning goes away, simularily I remove it and my reports run fine. I know the java flow has to do with java continuations, but when is this jar actually needed? We use subreports extensively in our reports and I thought that the jasperreports-javaflow is used by default (forget which version this was done), but when I remove it from the classpath my reports still run. Can some shed some light here? Thank you very much in advance! Post Edited by torrana at 07/07/2011 15:11