Build Number | Database | OS |
V10 build 3512 | MariaDB | Windows Server 2016 |
I installed V10 and see the following error message in the System Console of the Control Panel: “java.net.ConnectException: Connection refused: connect”. I wonder what is causing the error and how I should resolve it. The full output from the System Console is below:
Initialising startup options from startupOptions.props file
Overall status: Aware IM starting …
Process status: Aware IM Server: Starting…
Starting AwareIM Server C:/AwareIM/CP/eclipse/../../JDK\bin\java -Xmx2048m -Xms20m -classpath C:/AwareIM/CP/eclipse/../../lib/* ; C:/AwareIM/CP/eclipse/../../CustomJars/* com.bas.newcp.ServerStarterECP
Process status: Aware IM Server: OK
Process status: Tomcat: Starting…
Starting Tomcat server C:/AwareIM/CP/eclipse/../../JDK\bin\java -Xmx2048m -classpath C:/AwareIM/CP/eclipse/../../Tomcat/bin/bootstrap.jar;C:/AwareIM/CP/eclipse/../../Tomcat/bin/tomcat-juli.jar -Dcatalina.base=C:/AwareIM/CP/eclipse/../../Tomcat -Dcatalina.home=C:/AwareIM/CP/eclipse/../../Tomcat -Djava.io.tmpdir=C:/AwareIM/CP/eclipse/../../Tomcat/temp org.apache.catalina.startup.Bootstrap start
Connecting to URL http://localhost:80
Connecting to URL http://localhost:80
Connection to URL: first exception is Connection refused: connect
java.net.ConnectException: Connection refused: connect
(exception details left out here)
Process status: Tomcat: OK
Process status: Not started
Overall status: OK
My setup: AwareIM is installed on a VPS. I changed the Tomcat port from 8080 to 80 to be able to access the app (in development) using the standard http url.
The system settings in the configuration manager are below. Although I am not sure whether they are relevant, because I get the connection error after starting the Control Panel and BEFORE the Configuration Tool is actually started.

Last but not least: I installed V10 over the existing V9 installation - relying on the ‘Intelligent Installer’ which should not lose custom changes. It seems that the existing BASServer.Props and startupOptions.props files from V9 have been retained and don’t know whether this could mean that they do not contain a particular property that V10 is expecting.
Any suggestions would be appreciated.