Servoy 2026.6.0

Announcements
1

We are pleased to announce the availability of Servoy 2026.6.0 (release number 4182)

This version is available through the download site

See whats new for the global changes and the case list

An installation (coming from the normal installer or from a platform specific archive) is shipping with a Java VM (Java 25.0.1)

So for the platform specific archives you don’t need to install or have java on your system.

This release can be updated by using the “latest” url: http://download.servoy.com/developer/latest/ (when you come from 2019.03 or higher)
This release is build on Eclipse 2026.03 (4.39)

This is a release in our quarterly release cycle
if you want to stay on the LTS path you need to stick to 2025.03.x or the 2024.03.x LTS and enabled only the lts update site.
or if you want to move to an LTS release and you are on 2026.03 keep being on that release, the 26.3.1 LTS will be released soon

Many webpackages have new releases for the 2026.06. (this is needed because of the angular version that was updated, still a minor release but they had security releated fixes that caused regressions for us)

2

Hello,
We are using Servoy 2026.6.0 and cannot upload solutions because we receive the following message:
[error] com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: MaxOpenPreparedStatements limit reached

We are using MariaDB as the servoy_repository and have already increased the Maximum active connections to 300, but the problem persists.

This is urgent. Is there a solution to this problem, or do we have to revert to version 2025.12?

Thank you very much and best regards.

image
image1369×265 20.9 KB

3

why are you still importing a solution like that the old way?
This will not really be supported anymore very soon (and is still there to have a bit of backwards compartibility)

But this error is not about the connections, but about the max prepared statements that we make, this is also a setting on our server: server.0.maxPreparedStatementsIdle=100 (so it can be that this number needs to go down, that MariaDB doesn’t support many prepared statements cached)
Or you need to do the other way around that connections are not cached at all.. so not increasing the number to 300 but really say idle = 0;

4

Thanks, Jcompagner.

We were able to resolve the issue by increasing the value of server.o.maxPreparedStatementsIdle.

For now, we’re still importing our solutions using the .servoy files through the Solutions option because our product consists of multiple modules, and we’re not yet confident using the new deployment methodology. We believe we would benefit from some training to better understand the process.

Is there any training available, or could we arrange a training session with your team?

We’re also working on creating a WAR file that includes all of our solutions.

Corina Diez, from our team, is already in contact with Sean Devlin regarding this and a few other topics.

Thanks again!