Some of the operations you perform require an application restart to take affect. Depending on the specific type of operation, this can lead to heavy load upon restart execution.
The following article lists the various restart types in Sitefinity CMS, together with the operations that trigger them. The restart operations are ordered according to their performance overhead.
This operation unloads the application domain and resets the database model. You can perform full restart in one of the following ways:
Cleans application cache and reinitialize the system. This does not reset the database model. You can perform soft restart in one of the following ways:
This operations forces the metadata containers for each opened connection to be recreated.
You can perform database model restart by making any change in the dynamic types, dynamic fields, custom fields, or by adding or removing a language for the system.
NOTE: When a restart is triggered by the Sitefinity CMS application, a message for the restart operation is logged in the Trace.log file. You can find the Trace.log file in ~/App_Data/Sitefinity/Logs folder.
The message that Sitefinity CMS logs during a restart contains additional information about reason for the restart, the user that invoked the operation, a flag parameters of the restart method, etc.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2021 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity