OneClick WebApp failing to start with no error output

Products

• Network Observability
• Spectrum

Issue/Introduction

OneClick WebApp is failing to start and shows no error output in either:

$SPECROOT/webtomcat/bin/logs/webswing.log
$SPECROOT/tomcat/logs/stdout.log

Environment

DX NetOps Spectrum all currently supported releases

Cause

At the command line (bash -login in Windows), set the environment variable for JRE_HOME. So, on Windows:

set JRE_HOME=$SPECROOT\Java\jre

For example:

set JRE_HOME=d:\win32app\Spectrum\Java\jre

Then;

cd win32app\Spectrum\webtomcat\bin
catalina.bat run

If the following output error is generated:

01-Aug-2025 12:18:16.506 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector["https-openss1-nio-443"]]
       org.apache.catalina.LifecycleException Protocol Handler initialization failed 
               at org.apache.catalina.connector.initInternal(Connector.java:1027)
...
Caused by:java.net.BindException: Address already in use: bind

 

Then when WebTomcat is trying to start, it is trying to start on a port that is already taken and the above indicates that port is 443. By default, on Windows, Spectrum OneClick (Tomcat) starts on 443.

Resolution

Check in $SPECROOT/webtomcat/conf/server.xml

Identify the Connector for WebTomcat and check if it is set to start on port 443. For example:

<Connector port="443" enableLookups="true" disableUploadTimeout="true" tcpNoDelay="true" acceptCount="100" scheme="https" secure="true"
SSLEnabled="true" clientAuth="false" ssiProtocol="TLS" sslEnabledProtocols="TLSV1.2,TLSV1.3" ciphers="TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256"
keystoreFile="D:/win32app/Spectrum/custom/keystore/cacerts" keystorePass="password" keyAlias="tomcatss12">
</Connector>

If it is set to port 443, or any port on which another service is running, then this is incorrect as it will clash with that process/service and so the above port=".." should be set to 8443 (default on Windows).