Previous Next

Thread: Webservice Application Crashes

Last post 07-18-2008 3:12 PM by chuck.boyer. 3 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (4 items)

Sort Posts:

  • 07-18-2008, 8:20 AM

    • chuck.boyer
    • Not Ranked
    • Joined on 08-19-2004, 9:39 AM
    • Reston, VA
    • Posts 2

    Webservice Application Crashes

    I have a problem with a webservices application (.NET 1.1 running on IIS 6.0).  After approximately 9 hours it crashes and we receive HTTP/1.1 500 ( The specified network name is no longer available.  ) errors. 

    The only event in the event log that I can find that corresponds to the same timeframe is the following:

    Event Type:    Information
    Event Source:    W3SVC
    Event Category:    None
    Event ID:    1074
    Date:        7/17/2008
    Time:        9:15:03 PM
    User:        N/A
    Computer:    [mycomputername]
    Description:
    A worker process with process id of '10148' serving application pool '[mysite.tld]' has requested a recycle because the worker process reached its allowed processing time limit. 

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


    Does anyone have any suggestions on where to start looking for the problem?  I have downloaded the debugdiag tool, but I'm a bit unsure of how I should configure the rules to capture the crash.

     

    Thanks
    Chuck

     

    Chuck Boyer, MCSD .NET
    Director of Production and Development
    Edge Media Design
  • 07-18-2008, 10:22 AM In reply to

    Re: Webservice Application Crashes

    Chuck,

    Welcome to the IIS Technet Boards. 

     The message you are seeing in the Event logs points to some settings on the application pool for mysite.tld.  Do you have any of the options set for Recycling this application pool?  You can set these pools to recycle based on memory consumption, processor consumption and also time.  

    Do you have any of these settings?  If so, can you post them?

  • 07-18-2008, 11:04 AM In reply to

    • Rovastar
    • Top 10 Contributor
    • Joined on 03-13-2008, 10:00 AM
    • London, UK
    • Posts 758

    Re: Webservice Application Crashes

    Also more useful is to edit the registery so it display when the application pools recycling in the logs.

    "

    Normal 0 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}

    Additionally you can log when the app pools recycle. For some servers you have done this however you have not enable this for all events that can occur (you have only enabled: AppPoolRecycleTime, AppPoolRecycleMemory,  AppPoolRecyclePrivateMemory)

     

    It may be useful to have this for all events that occur.

    Complete list:

     

    AppPoolRecycleTime

    AppPoolRecycleRequests

    AppPoolRecycleSchedule

    AppPoolRecycleMemory

    AppPoolRecycleIsapiUnhealthy

    AppPoolRecycleOnDemand

    AppPoolRecycleConfigChange

    AppPoolRecyclePrivateMemory

     

    RecycleISAPIUnhealthly is useful to have.

     

    To turn them all on (for AppPool: DefaultAppPool):

     

    cscript adsutil.vbs Set w3svc/AppPools/DefaultAppPool/LogEventOnRecycle 255

      "
    Most overused word in IT is 'should' as in 'That should work!?!'
  • 07-18-2008, 3:12 PM In reply to

    • chuck.boyer
    • Not Ranked
    • Joined on 08-19-2004, 9:39 AM
    • Reston, VA
    • Posts 2

    Re: Webservice Application Crashes

    Thanks for the tips guys. Recycle worker process is set to every 720 minutes.  All other options are unchecked.

    I've enabled logging on the events suggested, so I'll keep an eye on things.

     

    I would think though that the auto recycling of the worker process shouldn't cause the application to crash.

    Chuck Boyer, MCSD .NET
    Director of Production and Development
    Edge Media Design
Page 1 of 1 (4 items)
Page view counter