We are pleased to announce the availability of Servoy 2024.3.6_LTS (release number 3949)
See 2024.3.6_lts_fixes for the list of fixes for this release since 2024.3.5
This version is available through the download site
or through the update site URL: http://download.servoy.com/developer/lts
If you want to use the LTS release enable the above LTS update site and disable the ‘latest’ update site so you only update to LTS updates.
You are strongly recommended to move over to one of the supported branches (2023.03 LTS or 2024.03 LTS or 2025 Latest)
if you are still on 2023 LTS please start upgrading to this one because support of 2023 will be ending in a few months.
For solutions that are already in production it is a good idea to stick to this version (2024.3.x)
This is the last release that has support for SmartClient, Webclient and NG1
Congratulations to you and the team!
(I really wanted to complain about "it’s not there, but I just noticed it’s been like 5 minutes, you’re probably still uploading right now…).
After deployment Servoy 2024.3.6_LTS war file and (re-)start Tomcat the Servoy license codes disappear from the servoy_properties file !!! We experience this on multiple servers.
we did a fix for this because servoy was constantly using the “cache” version (in the user.home dir of the server) which was incorrect, the once in the WAR should always be leading.
Are you guys not exporting the WAR with the correct license? Are you inserting a license after it is deployed?
and that is something we don’t really expect to happen, the WAR includes the license that is build The problem we fixed is that an old license was stored in the cached properties and because of that those where used and where not upgraded, even if the WAR had the correct license.
So we now make sure that those are cleaned out.
What should be done if you don’t want the license it the WAR is that you do specificy it it the war but then the values are Environment variables (or system properties) so they are substituted when the server loads.
The current version of Servoy doesn’t expect that the WAR doesn’t have anything and that those are really only in the server cached properties (we try to avoid having those at all, the WAR should just be it, config through environment or system properties)
We could maybe relax the code a bit, to not clean license stuff when the WAR properties doesn’t have any.. you can create a case for this.
Up to now, we could add Servoy licences after the deployment of a solution (war file) as appropriate. With version 2024.3.6_LTS, we have to add a license while exporting the war, which is not very convenient. If we have deployed that war file and later add additional licenses via the Servoy Admin Page, the licenses get lost after a server restart, which of course is not as expected. After several tests, we were not able to add or remove a license later on which is saved in the properties file. That’s very unconfortable and frankly annoying. Adding and removing licenses via the Servoy Admin Page used to work for decades, but now it seems broken and the menu Licenses in the Admin Page is therefore useless.
we improved this already for the next releases
If the war doesn’t contain a license we will not then remove it from the stored properties file on that server.
What still doesn’t work is that if you have licenses in the WAR and then also add more through the admin page, this is something we are not supporting anymore (because that caused problems the other way around that the WAR licenses where overwritten)
We for the most part assume that the WAR is a self contained, standalone configured item, that you should only configure from the outside through system or environment properties.
Thank you for your answer. There are still open questions for me:
Which is the new version you mentioned? We use Servoy 2024.3.6 LTS. Will there soon be an update available? When? We plan a deployment within the next two weeks.
You explain, that in that new release, the war does not have to contain licenses. And if there are non in the war, the ones (could be many) in the properties file are used. Is this correct?
You write about configuration from the outside through system or environment properties. What do you mean by that? Could you explain this in more detail? And does it include licenses?
that fixed this, that is currently only fixed for the 25.X releases but we can backport it if really needed (add a comment on that case)
there won’t be a 24.3.x release in 2 weeks we first focus on releasing 25.06 and after that the 25.3.2 LTS is first created.
(right after that we can do a 24 release)
That fix in that case makes sure if there are no licenses found in the WAR then it will just leave everything as is (so if there are licenses the the properties file of that server it will use that)
In a WAR you can just have 1 license, but that doesn’t have everything filled in but are just placeholders like ${license_key} so the WAR will find a license but by itself they are not valid.
But then when starting the WAR you can give that tomcat system properties -Dlicense_key=xxx or set environment variables like that in the container/server.
That means you can use the same war (dev, staging, production or even deployed multiply times at the same time) but then running with different licenses.
You just configure it from the outside
