I have a shared hosting account with 128MB of RAM and my site is in my app pool.
The site is low and fewer traffic is available, but I am getting the following error:
An application serving 'xxx v4.0 (classic)' application pool The worker process has requested a recycle because it reached its private bytes memory limit
This is often happening, which restarts the app pool. If the App Pool is restarted many times, it will eventually stop. Then when I go to the site, I get a 503 error.
Using data access from site F. and ADO.net, C # is using all my database connection statements and I There is complete confidence that they are being opened and closed properly.
I have spoken to the host and I can upgrade the RAM to 256MB which shows the site to run well. But I'm a little worried that just upgrading the RAM is a temporary problem masking the problem.
The debug is set to the wrong in web config and before I send files to the server to copy which I am creating for release
when I If I run the solution in Visual Studio, then my IIS worker process is about 100 MB.
I think my questions are:
> Can I copy my hosting environment to my local machine? Is this normal for a fairly small website for more than 128MB RAM?
I am trying to see if any help or guidance will be greatly appreciated if there is a slight loss.
Other potentially important information:
.NET Framework 4.5 web form AjaxControlToolkit is used (only for me the script is loaded)
I have seen many blog posts and similar questions but I have not made any progress is.
Thanks
Jim
This message is within the IIS It is about killing the config boundaries, it is not necessary that there should be anything with the amount of RAM on the host (although the settings set within IIS should keep your total RAM in mind, hence there is an indirect link ).
- Open IIS
- Left click on "Application Pool" <
- Find your dedicated pool and right-click on it, "Recycling .. Select "."
- "Check for private memory usage (in KB):" value
[These instructions on IIS 7.5 Based, but similar to other versions]
No comments:
Post a Comment