Reply to thread

Message

<blockquote data-quote="MJGraf" data-source="post: 1039779" data-attributes="member: 17886">ok, just did an install on a clean Win7 VM. Can confirm that install hangs - and most likely it is SQLiteDatabase, which makes it hang.What I suppose is the following:When the installer hangs, the MP2 Server Service is already started. This means that the database is already opened by the MP2 Server Service process. The installer then instatiates its own pluginmanager in its own process and enables all the plugins. This means that we more or less have all the plugins loaded a second time, just in another process. For SQLiteDatabase this means that a second process tries to open the same database - and this doesn't work because for performance reasons we open the database in exclusive mode in the MP2 Server Service process and so the installer process can't open it a second time.It should be easy to make a workaround for this, e.g. do not open the database if we are starting up in maintenance mode (that way the installer, which uses maintenance mode, will not try to open the database). But the question is whether it is really a good idea to more or less start up MP2 Server a second time in the installer process. I'm sure that over time there will be more plugins that don't like being executed twice on the same machine in two separate processes.@[USER=48495]morpheus_xx[/USER]: Any thoughts on this? Do we really need such a big part of MP2 Server started twice? Or is it possible to delay the start of the regular MP2 Server Service process until after we have called the CustomActions to make sure that at least we don't have two MP2 Servers running at the same time?Michael</blockquote>

[QUOTE="MJGraf, post: 1039779, member: 17886"] ok, just did an install on a clean Win7 VM. Can confirm that install hangs - and most likely it is SQLiteDatabase, which makes it hang. What I suppose is the following: When the installer hangs, the MP2 Server Service is already started. This means that the database is already opened by the MP2 Server Service process. The installer then instatiates its own pluginmanager in its own process and enables all the plugins. This means that we more or less have all the plugins loaded a second time, just in another process. For SQLiteDatabase this means that a second process tries to open the same database - and this doesn't work because for performance reasons we open the database in exclusive mode in the MP2 Server Service process and so the installer process can't open it a second time. It should be easy to make a workaround for this, e.g. do not open the database if we are starting up in maintenance mode (that way the installer, which uses maintenance mode, will not try to open the database). But the question is whether it is really a good idea to more or less start up MP2 Server a second time in the installer process. I'm sure that over time there will be more plugins that don't like being executed twice on the same machine in two separate processes. @[USER=48495]morpheus_xx[/USER]: Any thoughts on this? Do we really need such a big part of MP2 Server started twice? Or is it possible to delay the start of the regular MP2 Server Service process until after we have called the CustomActions to make sure that at least we don't have two MP2 Servers running at the same time? Michael [/QUOTE]

Verification