Page History

...

• Java WebStart console
• Java WebStart logging and tracing
• Checking the contents of the JNLP file that is used to start the Smart CientClient, by appending a "raw" parameter with the value "true" at the end of the URL of the JNLP file. With this extra parameter appended, the contents of the JNLP file will become the source of the web page, which can then be viewed in the browser:
  {serverURL}/servoy-client/{solutionName}.jnlp?raw=true
•  Server log: It can be that the Smart Client has issues due to something happening on the Servoy Application Server, thus it's important to also check the Application Server log when debugging Smart Client issues

Smart Client won't start

• The JNLP file gets downloaded as file: When this happens, it means can be one of two reasons:
  • The browser and/or the OS has not associated with Java WebStart: Associate the jnlp file extensions with Java WebStart 
  • Java/Java WebStart is not installed at all: Sun/Oracle Java Runtime environments ship with Java WebStart by default. Install a Sun/Oracle JRE to solve this issue
• Error: cannot find dataservice, it may not be running on server 
  This error is displayed in the Servoy Smart Client when it can't properly connect to the Servoy Application Server at startup. Most likely cause of this message is incorrect configuration of the Network Settings in combination with firewalls and proxies. See Network related settings for more information on configuring the network settings.
• Error: Connection to Servoy server is invalid
  Invalid SSL Certificate or using a self-signed certificate, which is not supported for Smart Clients. See Network related settings for more information on configuring SSL
• Error: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors 
  The Certificate used for SSL is issued by a Certificate Authroity (CA) that is not recognized by Java. For example certificates form startcom.org. The solution is to use a Certificate issues by a different CA that is trusted by Java
• Error: Java Web Start error: Problem downloading the application
  Something goes wrong in Java WebStart with downloading and starting the Smart Client. Check the Details tab for pointers

...

• Flush the solution on the Servoy Admin page: Each Solution listed on the Solutions page of the Servoy Admin page has a flush button. When clicked, the internal version id for the Solution is updated with a new value, indicating to connecting Smart Clients that a new version is available and should be downloaded 
• Remove the Smart CLient Client application from the Java WebStart cache: Cached applications can be removed from the cache through the Java Control Panel. See Client side settings through the Java Control Panel in the Smart Client chapter for more information
• Remove the temporary internet files from the Java WebStart cache: The WebStart JNLP file is also cached by WebStart in the temporary Internet files. If the above mentioned solutions fail, deleting the JNLP could be the last resort. See the Temporary Internet Files in the Java Control Panel.

Other Smart Client issues

...

You can review the list of plugins that are send to the client by adding "?raw=true" to the url of the Smart Client (http://domain:post/servoy-client/solutionName.jnlp) and then viewing the content of the JNLP file by looking at the source code of the page in the browser.

-----------------TODO------------------

Proxy Settings in Java Webstart, causing fallback to Direct Connection, for which requirements aren't met

Smart Client update issues

flush
remove app from java
remove temp internet files

...

----------------------

Database Connectivity

General

• Is the required JDBC driver available?

...

•  Servoy comes bundled with a limited set of JDBC drivers, due to licensing. For example, it is not allowed to bundle JDBC drivers of Oracle or the official Microsoft SQL server JDBC driver. See the database section of the Servoy stack info for a list of the shipped JDBC drivers. If no JDBC driver is listed for the database to which a connection needs to be made, it needs to be added manually. See Database Connectivity > JDBC Drivers for more details on which JDBC driver to use and how to add it.
• Is the database up and running?

...

•  While obvious that the database needs to be up and running in order for it to be used, it does happen quite often that the source of connectivity issues boils down to the database not being started. Note that the Servoy Application Server doesn't start any database!
• The Tables & views do not show up in Servoy Developer/errors on the server about missing tables/views while the connection itself seems to work

...

• : check that the schema and catalog properties of the database server settings are set correctly. These two properties are send to the database and based on those the database/JDBC driver filters the visible Tables/views for

...

• the connection

...

Oracle

When connecting to Oracle databases, make sure to use the correct version of the Oracle JDBC driver. Each Oracle database version has it's own version of a JDBC driver and when connecting to Oracle with a JDBC driver that was meant for another version of Oracle, the results can be mixed

• Servoy doesn't see the tables in the database

...

• : Most likely cause is the 'Schema' property for the connection. This property must be set to the appropriate 'Schema' in the Oracle database. The value for the 'Schema' property must be all uppercase when connecting to an Oracle Database.

SQL Server

• Failed to establish a connection

...

• : In order to connect to SQL Server using JDBC, the TCP/IP option of SQL server needs to be enabled, which it isn't by default. If this is the case, a error similar to the following can be found in the log: "com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed."
• System tables and Views show up in Servoy Developer, despite the "Skip System Tables" in the Database Server

...

• definition: This is a known issue with the SQL Server driver

MySQL

• Connection to database lost

...

• : MySQL is notorious for dropping idle connections after a certain timeout. This can be prevented by using the following  "validation query" for the Database Server connection: "select 1", at the cost of a little overhead. It's preferred to configure MySQL to use longer timeouts.