Re: Problem deploying a context (Servoy 8.2.3)
Posted: Tue May 15, 2018 10:07 am
Yes you either have to wait for 8.3.1 or go back to the previous version that you were using (unless we can identify why it happens specifically for you and you want to work around that - see below).
The problem was 2 threads blocking each other: one thread is the thread that loads in the background used servers/tables structure so that when they are accessed for the first time by solutions they load faster, and the other thread was the app. server startup that prepares solutions for usage. This problem appears if - for some reason - there is no column information in the repository for columns in multiple tables that are used by solutions. So you have to have multiple tables that have new columns that Servoy was previously unaware of. That doesn't usually happen as far as I know after server restart.
I managed to reproduce it by manually adding new columns to some of the tables while app. server was offline & putting some code breakpoints in place to simulate the deadlock.
Do you know how that happens in your case? So some of the tables used in your solutions/modules having columns that the Servoy repo. was unaware of at server startup.
The problem was 2 threads blocking each other: one thread is the thread that loads in the background used servers/tables structure so that when they are accessed for the first time by solutions they load faster, and the other thread was the app. server startup that prepares solutions for usage. This problem appears if - for some reason - there is no column information in the repository for columns in multiple tables that are used by solutions. So you have to have multiple tables that have new columns that Servoy was previously unaware of. That doesn't usually happen as far as I know after server restart.
I managed to reproduce it by manually adding new columns to some of the tables while app. server was offline & putting some code breakpoints in place to simulate the deadlock.
Do you know how that happens in your case? So some of the tables used in your solutions/modules having columns that the Servoy repo. was unaware of at server startup.