Page History

...

When the Servoy Application Server will not start, there are a few likely reasons for it:

• The Servoy Application Server cannot access the Servoy Repository database. As the Servoy Application Server required the Servoy Repository database to be available on launch, failure to connect to the database will prevent the Servoy Application Server from starting. The most likely reasons for the Repository Database not being accessible are:
  • The Database Server that hosts the Servoy Repository database is not running. Note that the Servoy Application Server does NOT start any database server!
  • The Database Server runs on another Server which cannot be reached by Servoy due to network configuration
  • The Database Server doesn't accept the JDBC connection the Servoy Application Server is trying to make. See #Database Connectivity for database specific trouble shooting.
  • Invalid configuration of the database server connection named "repository_server" in Servoy
  • No database server setup within Servoy with the name "repository_server"
• The Servoy Application Server fails to start after updating the SSL configuration or disabling SSL. Any property in the servoy.properties file that contains the word "password" is automatically encrypted using the SSL settings configured (if SSL is enabled). If the configuration is changed, the Servoy Application Server is unable to decrypt the passwords. The solution is to set the passwords back to plain text in the servoy.properties file and starting the server again.
  When this scenario happens, the following error appears in the console, when starting the Servoy Application Server in a console/command window: javax.crypto.BadPaddingException: Given final block not properly padded 
• The Servoy Application Server fails to start due to network errors that result from Java starting in IPv6 mode, while the network hardware actually runs on IPv4. The Servoy Application Server can be forced to start using IPv4 by adding '-Djava.net.preferIPv4Stack=true' to the startup command

Server crashes

The Servoy Application Server is very robust and is known for its stability and extreme long uptime. The Servoy Application Server is not likely to actually crash, in a sense that the entire process is killed. What can happen is that due to incorrect configuration the performance decreases to the point where it seems like the Servoy Application Server has become unresponsive.

...