...

• Database Connection pool exhaustion: The Servoy Application Server manages a pool of connections for each Database Server it is connected to. When the pool is dimensioned too small, requests from Servoy Clients must wait on echother to finish, reducing the performance. Errors like "java.util.NoSuchElementException: Timeout waiting for idle object" in the log indicate th4e Connection Pool being exhausted. For more information on connection pool configuration, see Connection pooling in the Database Connections chapter
• OutOfMemory exceptions: If the Servoy Application Server requires more memory than is configured maximum, OutOfMemory exceptions will be raised. When these type of exceptions occur two things can happen:
  • If the Application Server is ran as a Service using the Service Component, by default the Application Server will be automatically restarted. See Running the server as a serviceThe Server As A Service for more information.
  • If the Application Service is not ran as a Service using the Service component, OutOfMemory exceptions can reduce performance, cause random exceptions of all sorts and the integrity of business logic execution is compromised, as it's not guaranteed that each part of the business logic has properly executed. Thus OutOfMemory exceptions are to be taken serious and solved. See Memory Management for more information

...

The Servoy Application Server will not automatically restart itself, except when run using as a service using the Service component and OutOfMemory exceptions occur. See Running the server as a serviceThe Server As A Service for more information.

Servoy Smart Client troubleshooting

...

• 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 settingsRelated 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 settingsRelated 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

...

• One of the network components is closing the connection automatically. Most likely the network component is configured to automatically close inactive or long running requests. If altering the network setup is not an option, it's possible to lower the ping frequency between the Smart Client and the Server to make sure the connection remains active. Depending on the configuration of the Smart Client related Network setting, different settings might require updating. See Network related settingsRelated Settings for more information.

Smart Client performance issues

...

• Too little memory available: The Smart Client is a Java process and as such it needs to be explicitly told the maximum amount of memory it is allowed to use. For more information on memory management for Smart Clients see Smart Client memory management in the Memory Management chapter
• Connection issues: if the network connection is not stable, this could have a negative impact on the Smart Client performance. If for example a firewall or NAT router automatically starts closing connections because it can't handle many open connections, there will be a performance penalty due to the fact Servoy tries to use a connection that is already closed and then need to establish a new connection. By lowering the RMI Connection timeout the use of already closed connections can be prevented. See Network related settingsRelated Settings for more information RMI connection timeout
• Database connection pool exhaustion: When the solution that is run in the Smart Client required database access, it sends the request to the Servoy Application Server that in turn communicates with the database. It does so using a pool of connections. If all clients do more requests at the same time than the maximum allowed number of connections in the pool, the requests will take longer to execute, as they will be on hold untill a used connection is released back to the pool. For more information on Connection pooling, see Connection pooling in the Database Connections chapter 

...