Page History

...

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

Server automatically restarts 

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 service for more information.

Servoy Smart Client troubleshooting

...