Andrei Costescu wrote:It would be best to have a separate server for the repository - to make sure you data/logic and repository tables don't mix by mistake.
I suggest that you try to start over with an empty repository database. So fresh import.
Or delete the solution and it's modules once before import to see if that changes anything.
The times you mentioned for flush and first client start after flush seem much too high indeed. How many versions do you currently have on app. server for your solution/modules?
If after importing in a clean repository database it behaves the same way and you are able to provide the solution for testing then you should
create a case and mention this forum topic in it as well.
Andrei,
thanks for your answer...thanks as well to Harjo.
For sure I will give a try to do not do a flush after an app upgrade in the coming months.
Generally speaking I need to understand if this could be considered a bug or not.
The customer involved is using the appl since 2005 moving through Servoy V3 > V3.5 > V5.1 > V5.2 where is still now...
The installation is still the old Servoy standard installation using iAnywhere as DBserver with separate db for repository and user data.
A proposal to migrate to Servoy V7 was already done but the customer prioritized application improvements to migration of base software.
The installation is a pure Servoy deploy environment, no development; few external plugins are used from IT2BE.
I should add the PC where the appl is running is a special edition: it is a Bloomberg Workstation, one of those PC able to retrieve financial information from Bloomberg via Internet. My application is interfacing a dedicated Excel spreadsheet where financial "tickers" are collected in an organized way; that spreadsheet to properly work need the base software installed on this workstation (Bloomberg + FinCAD).
What is special in a PC like this? Just the keyboard and the software running all the time...for the rest is a standard one [i5, quadcore, 4GB ram, LSI raid controller, RAID array of HD (No SSD...)]
Yesterday I was installing last improvements to the application when I noticed there were 28 version already in the repository. The 28th of these versions was installed about one month ago as a maintenance release.
I decided to cleanup the repository and restart from fresh.
First I deleted all previous versions for all applications as well as modules (I unfortunately forgot styles...)
Then I stopped and restarted both the Servoy Server and SQL Anywhere Server.
After restart I imported the full application with all its modules. All version numbers became 1 while 3 styles took version 29.
Then I flushed ALL and tried to restart the appl with NO success: the
http://localhost:8080/servoy-client/ page opened, I clicked on the Servoy logo, the application opened taking the unusual long time of the first start...
I waited as long as 30 minutes then decided to do what I've always done in the past in this situation:
- brutally stopped with task manager the appl instance running.
- stopping servoy server and db server from windows services
- rebooting the machine
- checking both services were up'n running
- importing again as new version the appl software (they took versions 2 and 30 for styles)
- flushing all (it took more than 15 minutes to complete!)
- starting again the application for the first time after the upgrade (it took more than 5 minutes to start)
At this point the application begin to start as quick as usual (2-3 seconds).
I remember this behaviour consistent since Servoy 3.5 (Servoy < 3.5 was used for a short time...) but never had enough time to analyze it to decide if it is a bug or not...
There was a workaround so I survived not having a real issue for the end user.
Maybe we are able to complete the screening now!
Some more details:
- With each new Servoy version I started from fresh in a new directory with fresh databases always on iAnywhere
- Within the same Servoy version I never tried to switch the repository to a really new database freshly created; I always reused the same original db just deleting old appl versions and installing last version available.
Do you need any more informations?
Should I consider it a bug and open a case for it?
Ciao,
GIanni