I would prefer to wait to file the report until I can pinpoint the problem and possibly recommend a solution. I took the jar file out of my project. Instead, I included the source code from Jasper 3.0.0 into my project, built it, and ran it. The bug did not appear. This is, naturally, puzzling. When the bug appears in the .jar, the stack trace line numbers match the source code line numbers exactly, so I consider the possibility that the official .jar has separate code from the source tree to be very small. Next I am going to use the .jar and replace the affected class files with ones compiled from source one at a time to pinpoint the problem.