Tech Off Thread

3 posts

Forum Read Only

This forum has been made read only by the site admins. No new threads or comments can be added.

asp.net 2.0 application getting recycled

Back to Forum: Tech Off
  • User profile image
    devnull

    hey all

    i have an application hosted in a shared environment, that server has a limit on the application pool (virtual memory 250mb, physical 100mb), my application keeps getting recycled.

    this is the error in the event log:
    A worker process with process id of '3872' serving application pool 'testapp_aspnet20' has requested a recycle because it reached its virtual memory limit. 

    currently its only calling couple of stored procedures per page load, it also does couple of ajax calls using ajaxpro.dll.

    ive used performance monitor but cannot see any memory leaks.

    when i use performance monitor to monitor asp.net issue tracker starter kit (process w3wp.exe - private and virtual bytes) the numbers are very similar to my application.

    any ideas?

    Thanks

  • User profile image
    sundararajan

    As u said the Asp.Net worker process gets recycled if there is not enough memory available.

    Can you please post the code in ur page(if u have no issues) so that lets look in to some sort of optimisation, by deallocating the objects immediately after its use and things like that. or just mail it to sundararajanxgs@gmail.com (replace 'x' with a '.' -just to prevent spammers)


    regards,
    sundararajan.s

  • User profile image
    blowdart

    ScottGu posted a blog entry on this yesterday!

    What timing!

    Someone on a listserv recently asked whether there was a way to figure out why and when ASP.NET restarts application domains.  Specifically, he was looking for the exact cause of what was triggering them on his application in a production shared hosted environment (was it a web.config file change, a global.asax change, an app_code directory change, a directory delete change, max-num-compilations reached quota, \bin directory change, etc). 

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.