StackOverflow error when running reports using javaflow-6.4.1 jar

0

We are running into stackoverflow error when we try to generate reports. The error is occuring in the jasperreports-javaflow-6.4.1.jar which is running into infinite loop for some reason and errors out finally.

Did some research and found that we can use the standard jasper jar instead of jasperreports-javaflow-6.4.1.jar. Since we are currently using jasperreports-javaflow-6.4.1.jar from long time we are worried about switching the jar to standard jar as it may cause regression issues.

Is there a fix which went into the next version of the javaflow jar to fix this issue?

How safe it would be to use the standard jar instead of javaflow jar?

Please share your thoughts on this.

Following is the trace

Caused by: net.sf.jasperreports.engine.JRRuntimeException: java.lang.StackOverflowError
	at net.sf.jasperreports.engine.fill.JRFillSubreport.prepare(JRFillSubreport.java:874) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRFillElementContainer.prepareElements(JRFillElementContainer.java:537) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRFillBand.fill(JRFillBand.java:411) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRFillBand.fill(JRFillBand.java:386) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummaryNoLastFooterSamePage(JRVerticalFiller.java:1066) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummary(JRVerticalFiller.java:1025) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReportEnd(JRVerticalFiller.java:286) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReport(JRVerticalFiller.java:122) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:582) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.fill.JRFiller.fill(JRFiller.java:163) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.JasperFillManager.fill(JasperFillManager.java:474) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:875) ~[jasperreports-javaflow-6.4.1.jar:6.4.1]
	at com.reporting.Report.runReport(Report.java:291) ~[reporting.jar:?]
	... 208 more
Caused by: java.lang.StackOverflowError
	at java.util.AbstractMap.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.Objects.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.HashMap$Node.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.AbstractMap.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.Objects.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.HashMap$Node.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.AbstractMap.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.Objects.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.HashMap$Node.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.AbstractMap.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.Objects.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.HashMap$Node.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.AbstractMap.hashCode(Unknown Source) ~[?:1.8.0_121]
	at java.util.Objects.hashCode(Unknown Source) ~[?:1.8.0_121]
shridhar.kabbur's picture
Joined: Oct 9 2019 - 5:29am
Last seen: 2 weeks 8 hours ago

1 Answer:

2

The javaflow version is IMHO (!) just needed when you can't use threads (e.g. in some J2EE environments or wherever it's forbidden to create new threads). So if you are not in such an environment you actually could use the normal JasperReports.jar.-... 

But I doubt that this is the solution... I think the problem is somewhere else in your designs... I guess there are some forbidden SubReport calls on bands that can't overflow or some wrong stretching types, print-repeated stuff or even some recursive usage of wrong subreports?!?!

You should investigate some more time to track down the causing error.

hth + regards

C-Box

C-Box's picture
2250
Joined: Jul 19 2006 - 5:58pm
Last seen: 1 week 4 days ago
Feedback