Launching Spectrum WebApp page was directed to OneClick page
search cancel

Launching Spectrum WebApp page was directed to OneClick page

book

Article ID: 267857

calendar_today

Updated On:

Products

Network Observability Spectrum

Issue/Introduction

After upgrading Spectrum from v22.2.1 to v22.2.8, launching the WebApp page redirects to OneClick Page.

The following error is seen in the $SPECROOT/webtomcat/logs/catalina.out file:

2023-06-12 17:06:08,889 INFO  [Admin Websocket Service Timer] (AdminWebSocketServiceImpl.java:358) Websocket closed to server id [null], url [ws://OneClick:9443/spectrum]. Reconnect in 5000ms.
2023-06-12 17:06:10,143 WARN  [Admin Websocket Service Timer] (AdminWebSocketConnectionImpl.java:164) Websocket connection to server [ws://OneClick:9443/spectrum] is not open! Ignoring send message.
2023-06-12 17:06:13,889 INFO  [Admin Websocket Service Timer] (AdminWebSocketConnectionImpl.java:135) Starting websocket connection to server [ws://OneClick:9443/spectrum].
2023-06-12 17:06:13,894 ERROR [Admin Websocket Service Timer] (AdminWebSocketServiceImpl.java:290) Failed to connect websocket to server [ws://OneClick:9443/spectrum]! Failed to connect to websocket

The following error is seen in the $SPECROOT/webtomcat/bin/logs/webswing.log file:

2023-06-12 16:22:29,028 INFO  [Webswing Process Handler] (SwingProcessImpl.java:219) [oneclickwebapp_anonym_null_1686601347918] ERROR: Failed to connect websocket to server [ws://OneClick:9443/spectrum/oneclickwebapp/async/app-bin]! -> Connection failed. | 
2023-06-12 16:22:29,028 INFO  [Webswing Process Handler] (SwingProcessImpl.java:219) [oneclickwebapp_anonym_null_1686601347918] ERROR: Exiting application because it could not connect to server -> jakarta.websocket.DeploymentException: Connection failed.

Environment

Release : Any
Component: WebApp

Cause

The user changed the https port in the $SPECROOT/webtomcat/conf/server.xml from the default 9443 to 8483 but did not change the port in the $SPECROOT/webtomcat/webswing/webswing.config file

Resolution

Update the $SPECROOT/webtomcat/webswing/webswing.config file with the correct port. Then restart tomcat and webtomcat.