Hi all:
Servoy Server takes more than 20 min. to restart!
I suppose that Servoy has to scan all databases (in log I can see many warnings about “Table name XXX from server xxx is too long (>30 chars) – this is not supported by all databases”), but what can I do to reduce that (very very) long wait?
Regards,
What version of Servoy is this?
In older versions you really had to wait, for Servoy to scan all those database’s & tables (especially with LARGE database’s with MANY tables)
There is property, for that that you have to put into servoy-properties file.
I believe in newer versions, this was not necessary anymore.
It’s v7.4.0
juan.cristobo:
Servoy Server takes more than 20 min. to restart!
I’ve seen this due to lack of indexing on the repository database.
Please check your backend database for any slow queries.
Repository Database is created by Servoy Server, so I’ve never worried about it. What do I have to check?
juan.cristobo:
Repository Database is created by Servoy Server, so I’ve never worried about it. What do I have to check?
Not everything that’s being created is always right
Like I wrote: I’ve seen cases where configurations would fail because of slow queries in the repository database.
I don’t know which database you are using, but there are plenty tools out there to track slow queries.
And you probably can find those statistics in the system tables of your database too.
You should start tracking as soon as your application server starts.
If you see any slow queries you’ll need to reproduce them and scan them with a query planner.
That will give you inside information about which indexes should be added to solve it.
Again: I’ve seen this before, so it’s worth checking, but maybe there’s another likely cause in your configuration…
I’ve never seen 20mins for a Server restart - usually < 2mins - so it does indicate something pretty unusual.
If you have big systems with LOTS of releases then the Repository DB will grow quickly so may be worthwhile dropping/recreating.
The Repository DB is small (about 85MB) and the server is a fresh install.
In the Repository DB slow query log I see many slow queries in “servoy_columninfo” table. These slow queries are when Servoy reads info about an specific connection (MS Dynamics NAV backend DB). This DB has almost 6.000 tables and the name of many of them is long (>30 chars), so Servoy writes many warnings in the log.
Perhaps I could say Servoy not to scan db’s and tables at restarting…
juan.cristobo:
The Repository DB is small (about 85MB) and the server is a fresh install.In the Repository DB slow query log I see many slow queries in “servoy_columninfo” table. These slow queries are when Servoy reads info about an specific connection (MS Dynamics NAV backend DB). This DB has almost 6.000 tables and the name of many of them is long (>30 chars), so Servoy writes many warnings in the log.
Perhaps I could say Servoy not to scan db’s and tables at restarting…
Wow 6000, we have a DB that has 3700+ tables, (re)starting takes around 5 minutes, but servoy keeps scanning in the background for about 15minutes, but whilst scanning users can connect and start applications.
*edit
This is on servoy 6.1.5
Regards,
Peter
Peter de Groot:
(re)starting takes around 5 minutes, but servoy keeps scanning in the background for about 15minutes, but whilst scanning users can connect and start applications.
Not my server
As I said, it takes 20 min to restart, then users can connect, but server keeps scanning in the backgroud for hours
If I delete the connection to MS NAV DB, servoy takes a few minutes to restart, so I think that the problem is in that connection, but what can I do?
try this property in you servoy.properties file:
servoy.server.fastStartup=true
Another solution is, to create a special connection user, that ONLY ‘sees’ the tables you actually use!
I put that property in file, unsuccessfully (server took 25 min to restart
)
I just found an old email from Servoy, that this line was only for Servoy 5.2 and from Servoy 6 and up, it should do that automatically!
Please file a case…
juan.cristobo:
In the Repository DB slow query log I see many slow queries in “servoy_columninfo” table
Try to make them faster by analysing the query and adding the correct index…
I looked up an old issue and just give it a try by indexing ‘columninfo_id’ in this table…