When using the property -
It can error out when there are complex queries populating tables within a report.
On the surface it appears that this seems to be attempting some kind of page size estimation based on the data, which errors out if it encounters situations where the estimate is grossly over-estimated. The errors logged is (full stack attached) -
net.sf.jasperreports.engine.JRRuntimeException: Out of range start value 2147483647
I've been trying all afternoon to re-create this in a portable report, but without much success. At best I've had sporadic results, which indicates it may also be partly due to the information the database server is passing back to jasperreports.
A similar issue has been reported here -
This time the stack trace reporting a out of range error in the negative billions, likely a boundary of some sorts.
Unfortunately I don't have the source set up right now to debug further (and don't have a spare week to go through getting it all working properly :S). Hopefully someone in Jaspersoft can see where this issue might be occurring?