Clarity 14.2 (patch 5)
DB Oracle 11G
When trying to view one of the default reports, I get the following error.
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at
Any ideas why I'm getting this error?
I've double checked the configurations but can't seem to find what's missing.
Are you getting this on all OOTB reports or only Project Cost and Effort? Do you have the same issue when viewing the report on Jaspersoft server as opposed to CA PPM Embedded view?
Also, what is the exact Clarity version, have you installed any patches on 14.2?
I have seen similar entries when there was an issue to connect to the exact Datasource. In this case debug on com.jaspersoft.jasperserver.api.engine should help, for more information on how to enable it please refer to:Jaspersoft Tips and tricks : Part 2: How to troubleshoot Jaspersoft issues
I'm getting the error for many OOTB reports. I didn't have time to test ALL of them one by one.
I tried using superuser to login in jasper and view the reports, and the error is the same.
The version is: 184.108.40.206 05 12
I've upgraded from 13.3 to 14.2 and installed cumulative patch 5.
Okay, thanks, in this case it will be helpful for us to get some debug. Please enable debug on the NullPointer error as per above, then retry and provide your jasperserver.log for review. Thank you!
The client was in a hurry, so unfortunatelly I was forced to reinstall jasper entirely. I managed to solve the problem by doing so, and recreating the OOTB reports. Sorry for not being able to provide any valuable info on the issue, but thanks for trying to help. This information about troubleshooting will definetely be useful in the future.
Great, thanks for letting us know Bruno!
I ran into a Null Pointer exception on all Project-based reports a couple of months ago. What we found was that the encoding of one of the Input Controls had been changed. While we had checked/reviewed all of the reports, we'd not considered checking the Input Controls, which are developed separately from the reports themselves.
Before you go through all the input controls though, check a couple of your reports to see if you can find one or more common input controls - this would at least help you get started.
I raised a separate thread jaspersoft java.lang.NullPointerException as I did not find answer in this thread.