Dear all,
it is very important that the OC-server at time of startup can get connected to the configured "LocationServer" (and - in case Backup LS is configured to this too!). See parms set in ./tomcat/webapps/spectrum/META-INF/context.xml.
If name-resolution is not working - and/or there is a firewall issue - or there is any other reason the TCP-session etsablishment is not possible and/or may hang - then the OC-server startup will too. It then may appears the OC-server task is running but logon is not possible.
See: https://communities.ca.com/thread/241780199-upgrading-ca-spectrum-ft-paired-dss-oc-server-hang-issue
This happens on FT-paired Spectrum/SpectroSERVER install or just on standalone Spectrum install. Main issue is, that the OC-server will first try to get connected to the configured LocationServer(SpectroSERVER) hostnames - and once primary and backup is configured - it will check for both and may "hang".
As one symptom you will find the OC-server "service port" will be not opened in LISTEN status - even the OC-server task runs (http-bio* messages at stdout.log/catalina.out needs to be checked).
hth / kind regards, Joerg