Section 13th: Summary quartz.net Several deployment modes (IIS, EXE, service Deployment "with Topself, service class")

I. IIS Deployment

For example, in the MVC framework, the integration of quartz.net timed scheduling, the scheduling system will be suspended with the MVC framework under IIS, IIS will process recycling, so most Development will encounter quartz hangs in IIS for a period of time that is not useful.

Add: IIS can set a timed auto-recycle, and the default recycle is 1740 minutes, or 29 hours. IIS Auto-Recycle is equivalent to server IIS restart, application pool　　 memory is emptied, all data is purged, equivalent to IIS restart, in the measurement of fast development platform server side, in order to reduce the database burden, memory has staged a lot of information, not suitable for frequent recycling, Because of the loss of all in-memory data on the server, the recovery can cause problems in the program if it is not saved to the database in a timely manner. And if the system uses peak times, is not suitable for recycling, recycling may cause dozens of seconds IIS unresponsive, for the people who are working, is a very bad experience, will be considered to be a network or offline issues.

　　Solution: Close the recycle mechanism for the project's corresponding process pool on IIS.

　　How to turn off recycling for a process pool: Select the process pool for the projects deployed in IIS, and click "Advanced Settings" with 5 core parameters:

① garbage collection Occurs when configuration changes occur: If True, the application pool will not be reclaimed when configuration changes occur.

② fixed interval (minutes): After the set time elapses, the application pool is reclaimed, set to: 0 means that the application pool is not recycled. The system default setting is 1740 (29 hours).

③ Disable overlapping reclamation: If true, application pool recycling occurs to exit existing worker processes before another worker process is created

④ Request limit: The maximum number of requests that an application pool can handle before it is reclaimed. A value of 0 indicates that there is no limit to the number of requests that the application pool can handle.

⑤ generates a recycled event log entry: An event log entry is generated for each occurrence of a specified reclamation event.

Summary: Even though IIS process pool recycling can be turned off, it is still not recommended to hang quartz under IIS for long periods of time without a memory overflow problem.

Two. Common grammatical sugars

Two. Common grammatical sugars

Two. Common grammatical sugars

Section 13th: Summary quartz.net Several deployment modes (IIS, EXE, service Deployment "with Topself, service class")