nullpointerexception after 3.7->4.2.1 upgrade (this time, actually readible)

[dr_memory]

Good lord, this forum software made a complete hash of my last posting.  Let's try again:

After an upgrade from 3.7 on tomcat5.5 to 4.2.1 on tomcat6, about half of my reports are now generating NullPointerExceptions. 

The odd thing is that the failing reports use the same data source as the reports that still work, and I can manually execute their queries against mysql via the standard mysql client.

A representative stack trace is attached in full; the top of the trace is:

 

2011-11-18 15:39:57,343 ERROR errorPage_jsp,http-8080-6:344 - stack trace of exception that redirected to errorPage.jsp

java.lang.NullPointerException

        at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter.parameterHasValue(JRAbstractQueryExecuter.java:492)

        at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter.getBooleanParameter(JRAbstractQueryExecuter.java:530)

        at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter.getBooleanParameterOrProperty(JRAbstractQueryExecuter.java:559)

        at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.<init>(JRJdbcQueryExecuter.java:119)

        at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.<init>(JRTimezoneJdbcQueryExecuter.java:125)

        at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuterFactory.createQueryExecuter(JRTimezoneJdbcQueryExecuterFactory.java:50)

 

 

[satyadoorva]

 will need your jasper file 

[dr_memory]

You mean the JRXML file? Sorry, bit of a newb here. :)

[lucianc]

It's a bug that affects report units that define queries external to the JRXMLs.

The only workaround that I can think of is to avoid that case by embedding the queries in JRXMLs.

Regards,

Lucian

[dr_memory]

I've attached the JRXML file for this report.

If this is a known bug as per the last response, is there any sort of ETA for a fix?  Otherwise, I'm going to have to roll back to 3.7.

[lucianc]

The fix has been checked into the JasperReports Server SVN repository (details at http://jasperforge.org/projects/jasperserver/code) at revision 21639.

The fix will be included in the next release, but you can also patch and build the 4.2.1 sources to fix the problem locally.

Regards,

Lucian

[dr_memory]

lucianc
Wrote:

The fix has been checked into the JasperReports Server SVN repository (details at http://jasperforge.org/projects/jasperserver/code) at revision 21639. The fix will be included in the next release, but you can also patch and build the 4.2.1 sources to fix the problem locally. Regards, Lucian

 

 

Sounds good.  Is 4.2.2 planned to go out before the holidays this year?

[lucianc]

dr_memory
Wrote:

Sounds good.  Is 4.2.2 planned to go out before the holidays this year?

I don't have the details on the release schedule, but that's the rough time frame when 4.5 will be released.

Regards,

Lucian

[dr_memory]

A bunch of anouncements about 4.5 appear to have gone out, but the download links for japserserver are all still 4.2.1. Am I looking in the wrong place?

[lucianc]

JasperReports Server Professional 4.5 is out, but the community edition is still due.  I don't have an exact date unfortunately.