twoods Posted October 12, 2011 Share Posted October 12, 2011 Should we be using JRThreadSubreportRunner and only use JRContinuationSubreportRunner if we experience problems with the former? Or the other way around? Since philosophies can change as operating systems and hardware improve, what is the currently recommended option here?BACKGROUND:The Ultimate Guide 3 (page 168) seems to argue in favor of JRContinuationSubreportRunner over JRThreadSubreportRunner, so we have been using the JRContinuationSubreportRunner in production for about a year. However recently on servers running newer versions of the Sun 1.6 JVM with Tomcat we are consistently experiencing the StackOverflowError with complex sub-reports as described in detail these posts:http://jasperforge.org/projects/jasperreports/tracker/view.php?id=5015http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=79134&topid=91425We have applied the recommended solution of disabling the logging with no success.-Tad Link to comment Share on other sites More sharing options...
lucianc Posted October 12, 2011 Share Posted October 12, 2011 JRContinuaionSubreportRunner is meant to be used in environments that prohibit spawining new threads. When there's no such restriction, the default JRThreadSubreportRunner is a safer choice.Regards,Lucian Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now