OneClick WebApp fails to initialize with "Path not specified" error after upgrade

Products

• Network Observability

Issue/Introduction

After you upgrade to version 25.4.8, the OneClick WebApp fails to launch. When you inspect the webswing.log located in $SPECROOT/webtomcat/bin/logs/, you see the following initialization error: java.lang.IllegalStateException: org.webswing.exception.WsInitException: Invalid system property webswing.warLocation: Path not specified.

Environment

NetOps Spectrum 25.4.8

Cause

This issue occurs when the Webswing configuration entries are missing from the Tomcat properties file following the upgrade process. Without these entries, the Webswing cluster cannot locate the required application files or configuration settings.

Resolution

 

To resolve this issue, you must manually verify and add the missing configuration lines to the properties file:

1. Navigate to the $SPECROOT/webtomcat/conf/ directory on the OneClick server.
2. Open the catalina.properties file for editing.
3. Scroll to the end of the file and check for the Webswing configuration block.
4. If the following lines are missing, append them to the file:

webswing.warLocation=../webapps/spectrum.war
webswing.configFile=../webswing/webswing.config
webswing.tempDirBase=../webswing/tmp
webswing.propertiesFile.admin=webswing-admin.propertieswebswing.useGrizzly
WebsocketContainer=true
webswing.clusterWithSessionPool=true

1. Save the changes and exit the editor.
2. Restart the WebTomcat service to apply the configuration:
   • Execute $SPECROOT/webtomcat/bin/stopWebTomcat.sh
   • Execute $SPECROOT/webtomcat/bin/startWebTomcat.sh
3. Verify the WebApp functionality. If the application hangs or shows a "too many active connections" error, check $SPECROOT/webtomcat/bin/webswing-sessionpool.properties to ensure the webswing.server.websocketUrl uses the correct protocol (e.g., wss://####:9443/spectrum) and reflects the server's correct hostname.

Note: If you are using a security software suite (such as McAfee mcshield.exe), ensure it is not interfering with the installer's ability to write these configuration files during the upgrade process.