Launching a new site using aspnet zero and have winhost as host.
I kept getting an error 503 whenever I open 3 pages at once. Did some research and realized the app pool was recycling as it was going over the 300 megs limit they have. However I found if I manually changed the webconig from modules="AspNetCoreModuleV2" to modules="AspNetCoreModule" everything works fine and I can open dozen and dozens of windows all at the same time and never have app pool recycling issue.
Is this an expected behavior that with AspNetCoreModuleV2 it could cause this issue?
Any problems using AspNetCoreModule rather than AspNetCoreModuleV2?
8 Answer(s)
-
0
Does the web application have an error log? Or does the system event viewer have any information?
-
0
The host said all that was in the event viewer said the app pool was over 300 megs so it was recycling.
It takes about 5 refreshes of the dashboard with AspNetCoreModuleV2 set in the web.config to cause the host to recycle the pool (and hence freeze the site for 30 or so seconds).
I have the logs that are produced in app_Data/logs (from log4net I believe?). But not sure what I should be looking for other than it looks like it just gets shut down then starts reloading again.
DEBUG 2019-04-18 10:06:03,898 [26 ] Abp.Modules.AbpModuleManager - Shutting down has been started DEBUG 2019-04-18 10:06:03,900 [26 ] Abp.BackgroundJobs.BackgroundJobManager - Stop background worker: Castle.Proxies.BackgroundJobManagerProxy DEBUG 2019-04-18 10:06:03,901 [26 ] Abp.BackgroundJobs.BackgroundJobManager - WaitToStop background worker: Castle.Proxies.BackgroundJobManagerProxy DEBUG 2019-04-18 10:06:03,901 [26 ] Abp.Modules.AbpModuleManager - Shutting down completed. DEBUG 2019-04-18 10:06:05,979 [1 ] Abp.Modules.AbpModuleManager - Loading Abp modules... DEBUG 2019-04-18 10:06:06,006 [1 ] Abp.Modules.AbpModuleManager - Found 24 ABP modules in total.
If I do change web.config to AspNetCoreModule it runs great and have not been able to get it to crash (cause app pool to get over 300 megs). Not sure why that is or how these modules are different.
-
0
I have not found any information about this issue. Can you try another computer?
-
0
OK yes I just checked my local host and on both AspNetCoreModule and AspNetCoreModuleV2 my memory size of the core host goes up over 500megs just by opening a few pages.
Winhost said they have a 300 meg limit with the basic hosting package. They said the enterprise level has a 500 megs limit but based on what I am seeing it would go over that also and be forced to recycle.
Am I missing something when compiling? What does the memory typically run?
-
0
-
0
Generally this problem does not occur. So I suggest you try to change the computer.
-
0
How many should I try? This is two servers now that have had problems making the software unusable. What is the normal memory usage? I can try another host but this is a clean new install with no mods. You said "generally" does that mean that it does sometimes blow up memory like this?
-
0
The host has a memory limit by having found the cause by remote. Waiting for the best solution.
