Page History

Servoy Application Server

...

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

• Is the database containing the Servoy Repository running? 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
  doesn't start a database, not even the bundled PostgreSQL database.Does the application Server fail to start after disabling or updating the SSL settings? The passwords of the database connectiosn defined of the server and stored
  • does NOT start any database server!
  • The Database Server runs on another Server which cannot be reached by Servoy due to network configuration
  • 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 are that contains the word "password" is automatically encrypted using the SSL settings . due to the update to the SSL settings, the passwords cannot be decrypted anymore. Remedy: manually reset the passwords 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: see previous itempadded 

If the above mentioned items are not the the reason for the Servoy Application Server not starting, the next step would be to analyse the Application Server log files :

...

located in {servoyInstall}/application_server/servoy_log.txt

Network errors

Some Java environments start with IPv6 Stack. If this happens, while actually running IPv4, the result might be network errors. In order to prevent errors, the Servoy Application Server can be started with a preference to use the IPv4 Stack.

...