Troubleshooting Mango Server-Side Null Pointer Errors

You select a point for a server-side graphical component and the panel shows only Error:. The same point works in an analog graphic or another component, while catalina.out records java.lang.NullPointerException at com.serotonin.mango.view.component.ScriptComponent.addDataToModel(ScriptComponent.java:75). Start with the server-side script path. Replacing working points or changing browsers attacks the wrong layer.

Start at the failure boundary

Reproduce the fault once, then read the matching Tomcat log entry. Use the exception location to decide which branch to follow.

The browser receives the short DWR failure response, but the exception originates inside Tomcat. Switching among Internet Explorer, Safari, or Firefox does not repair a server-side null reference.

Prove the point path first

Select one failing point and place it in an analog graphic or another known-working component. Record whether the component displays a current value.

• If it works, keep that point as the control sample. Its successful rendering proves that Mango can resolve it through at least one component path.
• If it fails everywhere, stop this decision tree and diagnose the point itself. Check whether it is enabled, currently valued, and readable by the active user.
• If one point works but several others do not, compare their types and current value states before treating the problem as a global JavaScript failure.

Testing numerous points inside the same failing server-side component adds little information. A common exception at the same method and line shows that the component path, not point selection alone, is the useful boundary.

Test the JavaScript engine with a Meta point

Create a temporary Meta data source, add one point, and assign a minimal script that returns a value. This is the first discriminating runtime test because the suspected failure is JavaScript engine creation or execution inside the JVM.

1. Create the Meta data source without modifying the production point hierarchy.
2. Add a temporary Meta point.
3. Give the point a minimal script that produces a predictable value.
4. Run the point and inspect both its value and catalina.out.
5. Delete or disable the temporary diagnostic objects after testing.

If the Meta point evaluates correctly, the JVM can execute JavaScript. Move next to the installed Mango version and the server-side component configuration. If the Meta point cannot evaluate, work on the Java runtime and its JavaScript execution capability before rebuilding graphical components.

A Meta-point failure is more useful than another browser test. Both Meta calculation and the failing component depend on server-side script execution, while browser choice does not change the JVM engine loaded by Tomcat.

Verify the deployed build and runtime

Record exact values from the running server. Do not rely on a label such as “latest stable.” The affected installation reported Linux, Java 1.6, and Tomcat 6; Mango 1.6.4 was identified as the current Mango release for this case.

1. Read the deployed Mango version from the running application or its startup information.
2. Compare it with 1.6.4. If it is older, treat application version as an unresolved branch.
3. Confirm which Java executable actually launches Tomcat. A separate interactive Java installation does not prove which JVM the service uses.
4. Capture the complete exception, including every Caused by section and the first application frames.
5. Search the startup log for script-engine initialization errors that occurred before the DWR request.

The visible DWR warning is the transport-level report of the failed method call. The actionable frame is ScriptComponent.addDataToModel(ScriptComponent.java:75). Reconfiguring DWR or repeatedly restarting Tomcat wastes time when every request fails deterministically at that same frame.

Apply the resolving branch

Choose the correction from the Meta-point result and the version check.

1. If Meta scripting fails, correct the JavaScript execution environment used by the Tomcat service. Verify the service JVM selection and review its startup diagnostics for engine creation failures.
2. Restart Tomcat after changing the runtime so the web application creates its scripting resources under the corrected JVM.
3. Run the Meta point again before opening the graphical view. Do not proceed until it returns its predictable value without a scripting exception.
4. If Meta scripting works but the deployed Mango build predates 1.6.4, move to the cited current build using the product's supported upgrade procedure and preserve the existing configuration first.
5. If Meta scripting works on 1.6.4, recreate only the affected server-side component and select the known-good control point. If the exception remains at line 75, retain the component definition and full trace for escalation.

Do not rebuild all points, flatten the point hierarchy, or change client browsers before completing these branches. Those changes add variables without testing the server-side object that is null.

Verify the repair under the same request

Repeat the original action, not merely a login or page load.

1. Open the same graphical view.
2. Add the same server-side component.
3. Select the control point that previously produced Error:.
4. Confirm that the component accepts the point and renders its value.
5. Test at least one additional point that failed before the correction.
6. Inspect catalina.out for a new NullPointerException, DWR method-execution failure, or JavaScript initialization error.

The repair passes only when the original server-side selection succeeds and no matching exception is generated. A working analog graphic alone remains a control test, not proof that ScriptComponent recovered.

FAQ