-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Dimitri Kargapolov
committed
Aug 13, 2021
1 parent
1f71c51
commit d3a45e3
Showing
1 changed file
with
5 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,5 @@ | ||
WIP | ||
As you may know the VirtoCommerce platform does a lot of work every start: check modules versions, files in probing path, copy modules files to probing path if they absent or have inappropriate versions, and so on. It coulld take time for the application to complete all of the necessary operations and be ready to work. Sometimes, especially on machines with low resources, you could see that the application failed to start and throwed the following error: `HTTP Error 500.30 - ANCM In-Process Start Failure`. | ||
|
||
What is the solution? | ||
|
||
From the VirtoCommerce platform version 3.27.0 there is an option `VirtoCommerce:RefreshProbingFolderOnStart` to avoid checking the probing path at the platform startup. This can decrease startup time at least by a third. If the option set to `false` and the probing path exists, the platform will start with the current probing path content on an “AS IS” basis. It is assumed that the probing path contains consistent module files. If the probing path is absent, then the platform will start as usual, with module discovering/copying, with no look at the option value. |