Asp.net IIS6 - application pool recycle











up vote
2
down vote

favorite












I'm running an ASP.NET website on Windows 2003 IIS 6.0



Every 24-28 hours I'm getting the following error:



When the error occurrs all users are disconnected from the website.



Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 02/02/2010
Time: 19:29:38
User: N/A

A process serving application pool 'DefaultAppPool' exceeded time limits during
shut down. The process id was '1660'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Any idea what does the error means?



Is this related to application pool recycle?



If so, is it a "must" to recycle the IIS app pool?










share|improve this question
























  • Possible duplication: stackoverflow.com/questions/411918/iis-apppool-error-1013-w3svc
    – Zhaph - Ben Duguid
    Feb 2 '10 at 22:57












  • not quite the same as the other is a forced recycle by IIS, this is a normal recycle.
    – TheAlbear
    Feb 9 '10 at 12:46










  • Forced or not, application pool recycle is there, and you should then avoid in-process session mode (which means the new worker process does not keep previous sessions). That change of design can guarantee you won't get "all users are disconnected from the website". The latter is an issue, while the recycle is innocent.
    – Lex Li
    Dec 17 '14 at 8:11










  • Did one of the answers answer your question?
    – John Saunders
    Jun 23 '15 at 1:16















up vote
2
down vote

favorite












I'm running an ASP.NET website on Windows 2003 IIS 6.0



Every 24-28 hours I'm getting the following error:



When the error occurrs all users are disconnected from the website.



Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 02/02/2010
Time: 19:29:38
User: N/A

A process serving application pool 'DefaultAppPool' exceeded time limits during
shut down. The process id was '1660'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Any idea what does the error means?



Is this related to application pool recycle?



If so, is it a "must" to recycle the IIS app pool?










share|improve this question
























  • Possible duplication: stackoverflow.com/questions/411918/iis-apppool-error-1013-w3svc
    – Zhaph - Ben Duguid
    Feb 2 '10 at 22:57












  • not quite the same as the other is a forced recycle by IIS, this is a normal recycle.
    – TheAlbear
    Feb 9 '10 at 12:46










  • Forced or not, application pool recycle is there, and you should then avoid in-process session mode (which means the new worker process does not keep previous sessions). That change of design can guarantee you won't get "all users are disconnected from the website". The latter is an issue, while the recycle is innocent.
    – Lex Li
    Dec 17 '14 at 8:11










  • Did one of the answers answer your question?
    – John Saunders
    Jun 23 '15 at 1:16













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I'm running an ASP.NET website on Windows 2003 IIS 6.0



Every 24-28 hours I'm getting the following error:



When the error occurrs all users are disconnected from the website.



Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 02/02/2010
Time: 19:29:38
User: N/A

A process serving application pool 'DefaultAppPool' exceeded time limits during
shut down. The process id was '1660'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Any idea what does the error means?



Is this related to application pool recycle?



If so, is it a "must" to recycle the IIS app pool?










share|improve this question















I'm running an ASP.NET website on Windows 2003 IIS 6.0



Every 24-28 hours I'm getting the following error:



When the error occurrs all users are disconnected from the website.



Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1013
Date: 02/02/2010
Time: 19:29:38
User: N/A

A process serving application pool 'DefaultAppPool' exceeded time limits during
shut down. The process id was '1660'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Any idea what does the error means?



Is this related to application pool recycle?



If so, is it a "must" to recycle the IIS app pool?







asp.net iis-6 windows-server-2003






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 14 '11 at 11:48









SteveC

6,3711869121




6,3711869121










asked Feb 2 '10 at 18:22









RuSh

75541638




75541638












  • Possible duplication: stackoverflow.com/questions/411918/iis-apppool-error-1013-w3svc
    – Zhaph - Ben Duguid
    Feb 2 '10 at 22:57












  • not quite the same as the other is a forced recycle by IIS, this is a normal recycle.
    – TheAlbear
    Feb 9 '10 at 12:46










  • Forced or not, application pool recycle is there, and you should then avoid in-process session mode (which means the new worker process does not keep previous sessions). That change of design can guarantee you won't get "all users are disconnected from the website". The latter is an issue, while the recycle is innocent.
    – Lex Li
    Dec 17 '14 at 8:11










  • Did one of the answers answer your question?
    – John Saunders
    Jun 23 '15 at 1:16


















  • Possible duplication: stackoverflow.com/questions/411918/iis-apppool-error-1013-w3svc
    – Zhaph - Ben Duguid
    Feb 2 '10 at 22:57












  • not quite the same as the other is a forced recycle by IIS, this is a normal recycle.
    – TheAlbear
    Feb 9 '10 at 12:46










  • Forced or not, application pool recycle is there, and you should then avoid in-process session mode (which means the new worker process does not keep previous sessions). That change of design can guarantee you won't get "all users are disconnected from the website". The latter is an issue, while the recycle is innocent.
    – Lex Li
    Dec 17 '14 at 8:11










  • Did one of the answers answer your question?
    – John Saunders
    Jun 23 '15 at 1:16
















Possible duplication: stackoverflow.com/questions/411918/iis-apppool-error-1013-w3svc
– Zhaph - Ben Duguid
Feb 2 '10 at 22:57






Possible duplication: stackoverflow.com/questions/411918/iis-apppool-error-1013-w3svc
– Zhaph - Ben Duguid
Feb 2 '10 at 22:57














not quite the same as the other is a forced recycle by IIS, this is a normal recycle.
– TheAlbear
Feb 9 '10 at 12:46




not quite the same as the other is a forced recycle by IIS, this is a normal recycle.
– TheAlbear
Feb 9 '10 at 12:46












Forced or not, application pool recycle is there, and you should then avoid in-process session mode (which means the new worker process does not keep previous sessions). That change of design can guarantee you won't get "all users are disconnected from the website". The latter is an issue, while the recycle is innocent.
– Lex Li
Dec 17 '14 at 8:11




Forced or not, application pool recycle is there, and you should then avoid in-process session mode (which means the new worker process does not keep previous sessions). That change of design can guarantee you won't get "all users are disconnected from the website". The latter is an issue, while the recycle is innocent.
– Lex Li
Dec 17 '14 at 8:11












Did one of the answers answer your question?
– John Saunders
Jun 23 '15 at 1:16




Did one of the answers answer your question?
– John Saunders
Jun 23 '15 at 1:16












2 Answers
2






active

oldest

votes

















up vote
0
down vote













Yep this is IIS running a clean up, and recycling the app pool. you can change how this works by changing the setting on the applicationn pool..



IIS 6 Configuring Worker Processes for Recycling






share|improve this answer




























    up vote
    0
    down vote













    This can also be caused by deadlocks on the threadpool for your application. You may need to adjust the worker threads in your machine.config or alter that recycling settings adjust how often/when the recycling occurs based on processes or virtual memory.



    Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications






    share|improve this answer





















    • Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
      – Lex Li
      Dec 17 '14 at 8:13











    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f2186541%2fasp-net-iis6-application-pool-recycle%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    Yep this is IIS running a clean up, and recycling the app pool. you can change how this works by changing the setting on the applicationn pool..



    IIS 6 Configuring Worker Processes for Recycling






    share|improve this answer

























      up vote
      0
      down vote













      Yep this is IIS running a clean up, and recycling the app pool. you can change how this works by changing the setting on the applicationn pool..



      IIS 6 Configuring Worker Processes for Recycling






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        Yep this is IIS running a clean up, and recycling the app pool. you can change how this works by changing the setting on the applicationn pool..



        IIS 6 Configuring Worker Processes for Recycling






        share|improve this answer












        Yep this is IIS running a clean up, and recycling the app pool. you can change how this works by changing the setting on the applicationn pool..



        IIS 6 Configuring Worker Processes for Recycling







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 9 '10 at 12:45









        TheAlbear

        3,72274176




        3,72274176
























            up vote
            0
            down vote













            This can also be caused by deadlocks on the threadpool for your application. You may need to adjust the worker threads in your machine.config or alter that recycling settings adjust how often/when the recycling occurs based on processes or virtual memory.



            Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications






            share|improve this answer





















            • Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
              – Lex Li
              Dec 17 '14 at 8:13















            up vote
            0
            down vote













            This can also be caused by deadlocks on the threadpool for your application. You may need to adjust the worker threads in your machine.config or alter that recycling settings adjust how often/when the recycling occurs based on processes or virtual memory.



            Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications






            share|improve this answer





















            • Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
              – Lex Li
              Dec 17 '14 at 8:13













            up vote
            0
            down vote










            up vote
            0
            down vote









            This can also be caused by deadlocks on the threadpool for your application. You may need to adjust the worker threads in your machine.config or alter that recycling settings adjust how often/when the recycling occurs based on processes or virtual memory.



            Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications






            share|improve this answer












            This can also be caused by deadlocks on the threadpool for your application. You may need to adjust the worker threads in your machine.config or alter that recycling settings adjust how often/when the recycling occurs based on processes or virtual memory.



            Contention, poor performance, and deadlocks when you make Web service requests from ASP.NET applications







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Feb 9 '10 at 12:53









            Joel Etherton

            33.2k87094




            33.2k87094












            • Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
              – Lex Li
              Dec 17 '14 at 8:13


















            • Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
              – Lex Li
              Dec 17 '14 at 8:13
















            Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
            – Lex Li
            Dec 17 '14 at 8:13




            Unless further information is collected, I personally don't think it is a good idea to follow that KB article. Such warnings in event logs are generally harmless (if no other errors are observed at the same time).
            – Lex Li
            Dec 17 '14 at 8:13


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f2186541%2fasp-net-iis6-application-pool-recycle%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            The Sandy Post

            Danny Elfman

            Pages that link to "Head v. Amoskeag Manufacturing Co."