The on-screen output of the installer as well as the installation log contained within CA_VNA_Install_bak folder shows similar to the below entries:
Auditing database
Cleaning Stale Perspectives
DONE
Waiting for wildfly to start...
Create MySQL data source in Wildfly
MySql DataSource Successfully added to Wildfly
Waiting for wildfly to start...
Installing the Gateway WAR file
Installing the Open Collector
Restoring Wildfly SSL config
Successfully restored the SSL config in wildfly
Waiting for wildfly to start...
Timed-out waiting for wildfly to start
VNA / SDX utilizing Red Hat OpenJDK 17 and either set up with HTTPS or has certificates in its truststore that it needs to reference.
This is specific to a Red Hat based OpenJDK changes that increased its hardening.
To find what vendor your Java release is, you can run the following command after navigating to the bin directory of the Java installation:
java -XshowSettings:properties -version 2>&1 | grep 'java.vendor'
For example:
$ java -XshowSettings:properties -version 2>&1 | grep 'java.vendor'
java.vendor = Red Hat, Inc.
java.vendor.url = https://www.redhat.com/
java.vendor.url.bug = https://access.redhat.com/support/cases/
java.vendor.version = (Red_Hat-17.0.12.0.7-1)
CA_VNA_Install_bak folder within the installation source directory.mv CA_VNA_Install_bak CA_VNA_Installexport WILDFLY_PROTOCOL='https'export JBOSS_CLI="$WILDFLY_DIR/bin/jboss-cli.sh --connect -Djavax.net.ssl.trustStore=$VNA_KEYSTORE_FILE -Djavax.net.ssl.trustStorePassword=$WILDFLY_SSL_PASSWORD"./install.shThis has been resolved with VNA 24.3.11+