Notifications do not load in FrontEnd (FE)/UI

Products

• VMware Smart Assurance

Issue/Introduction

Unable to connect to Notification Log in the User Interface to view notifications and  not able to get device data on W4NET frontend

User notices error like below in logs.

NOTE: This is not the only logging seen however user may notice other errors as well for notification not loading in FE.

mashupengine.log:

ERROR http-nio-58080-exec-7 [.mashupengine.controllers.HomeController]  - Error processing invokeJSMashup.
javax.script.ScriptException: TypeError: null has no such function "indexOf" in <eval> at line number 529
    at jdk.nashorn.api.scripting.NashornScriptEngine.throwAsScriptException(NashornScriptEngine.java:470) ~[nashorn.jar:?]
    at jdk.nashorn.api.scripting.NashornScriptEngine.invokeImpl(NashornScriptEngine.java:392) ~[nashorn.jar:?]
    at jdk.nashorn.api.scripting.NashornScriptEngine.invokeFunction(NashornScriptEngine.java:190) ~[nashorn.jar:?]

.

.

Caused by: jdk.nashorn.internal.runtime.ECMAException: TypeError: null has no such function "indexOf"
    at jdk.nashorn.internal.runtime.ECMAErrors.error(ECMAErrors.java:57) ~[nashorn.jar:?]
    at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:213) ~[nashorn.jar:?]
    at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:185) ~[nashorn.jar:?]
    at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:172) ~[nashorn.jar:?]

smarts-edaa.log:

2025-01-24 09:48:19,958 ERROR XmlUtils http-nio-8080-exec-8 java.net.ConnectException: Connection timed out (Connection timed out)  
java.net.ConnectException: Connection timed out (Connection timed out)
    at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]
    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[?:?]

Environment

Watch4net/M&R - 7.x

Smarts - 10.1.x

Cause

MnR/Watch4net server is configured to use http/8080 however SM_CAS_SERVER attribute is configured in Smarts' runcmd_env.sh file hence output of smarts-edaa and alerts-edaa are redirected to CAS.

Resolution

As per the document Configuring SAM environment variables to support SSL SM_CAS_SERVER and SM_TOMCAT_SERVER are required while both Smarts and MnR are configured to use https/8443.

Remove both configured parameters, restart tomcat in Smarts and MnR would fix the issue of notification loading.