Jump to content
We've recently updated our Privacy Statement, available here ×

How to fix Unknown Source error?


saigkill

Recommended Posts

Hello,

currently i'm trying to get a report to run. Actually i'm getting:

22-May-2018 16:50:18.531 INFORMATION [ajp-nio-8009-exec-5] com.engomo.server.licence.LicenceValidator.isClientAllowedToConnectInternal re-connect from client "MyFlow365_1"(DA026B41-DEF0-420C-8478-CAD7F077867E1023786)22.05.2018 16:38:4122-May-2018 16:51:02.320 SCHWERWIEGEND [ajp-nio-8009-exec-7] net.sf.jasperreports.engine.fill.JRFillSubreport.prepare Fill 1: exceptionjava.lang.NullPointerException                at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReport(JRVerticalFiller.java:138)                at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:551)                at net.sf.jasperreports.engine.fill.BaseReportFiller.fill(BaseReportFiller.java:393)                at net.sf.jasperreports.engine.fill.JRFillSubreport.fillSubreport(JRFillSubreport.java:728)                at net.sf.jasperreports.engine.fill.JRSubreportRunnable.run(JRSubreportRunnable.java:58)                at net.sf.jasperreports.engine.fill.AbstractThreadSubreportRunner.run(AbstractThreadSubreportRunner.java:216)                at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)                at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)                at java.lang.Thread.run(Unknown Source)

 

Can anyone help me to identify the problem?

Main Report: https://pastebin.com/C4DuEdN6Subreport: https://pastebin.com/LiJiKJNTSubreport: https://pastebin.com/T7mY7rDG[/code]

 

Link to comment
Share on other sites

  • Replies 3
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Step by step.

Try delete subreport 2 from main report and run main report again. Will the error appear again in this case?

It is very strangely use $F{fieldName} at band Last Page Footer. It seems all fields equals null in this band. So expression $F{SHeft}.equals(Boolean.TRUE.toString()) can generate NPE.
Use "Yoda condition" to avoid such NPE. For instance change expression to (Boolean.TRUE.toString()).equals( $F{SHeft})

HTH

 

Link to comment
Share on other sites

Hi. Thank you very much for answering. I tried to replace ($F{SHeft}.equals(Boolean.TRUE.toString())) ? "Ja" : "Nein
with your proposed (Boolean.TRUE.toString()).equals($F{SHeft}. Sadly i'm getting the same error again.

That are the current used reports:

Main: Bewertung.jrxml: https://pastebin.com/mMvSLYWLSub: BewertungBild2.jrxml: https://pastebin.com/Tqvwed6FSub: BewertungMinder.jrxml: https://pastebin.com/XahE2kduMain: LGutachten.jrxml: https://pastebin.com/xCdPC7zkSub: LGBild2.jrxml: https://pastebin.com/gp3LhCiCSub: LGutachtenMinder.jrxml: https://pastebin.com/ThcyyL6K[/code]

It fails now each time if its running. Maybe anyone can imagine what happens?

 

Link to comment
Share on other sites

  • 1 year later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...