Databases
StackOverflow2013
Postsdbo
POWeb Service dying after an hour
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWeb Service dying after an hour
    primarykey
    data
    text
    <p>Recently we have upgraded our main product to be an ASP.NET 4.0 Project (upgraded from 2.0). This project is the main source of traffic to the web service, the other forms have not changed in this release. The web service has been running without issue for a couple years now. </p> <p>Following the release of the 4.0 environment to our main product our web service starting to die after about an hour and would do nothing but timeout until we restarted the worker process. </p> <p>We have changed it so that the web service was also in the 4.0 Framework. However this did nothing. Other possible attempts we have tried have also failed such as making it a service instead of a web reference, and updating our certificate validation to also use the proper/current framework techniques. </p> <p>The worst part is that there is no log in the event viewer being created so I have no leads as to what the problem is. We have applied a band-aid solution of recycling the app pool every 20 min (the recompile takes a second as the web service is very small) and it seems to be holding for now, but we would rather fix the problem than rely on this. So does anyone have any additional idea/suggestions as to where our problem may be coming from? Or anyone experience anything similar? </p> <p>Both projects exist in the same web farm and all machines are using IIS 6 32 bit. </p> <p>Thanks!</p> <p>edit- Some more info, The web service has a couple basic functions: </p> <p>1 - accepts XML documents loads them into a dataset then updates internal DBs with the information sent - and simply returns true </p> <p>2 - receives a request for processed data through XML and queries the DB for it builds XML response and sents it out</p> <p>3 - receives a confirmation that the data requested in step 2 was recieved and deletes it from the DB</p> <p>4 - hits a function that updates a DB so we can monitor some applications on our clients systems. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJohn
    1. USJohn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWeb Service dying after an hour
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUnlike the answer suggesting using Process Explorer, I'd suggest running Process Monitor when it stops working. You can limit it only to watch the relevant processes. Process Monitor will maybe allow you to see what makes the Service die. Process Explorer will probably only let you see that it died.
      singulars
      1. POWeb Service dying after an hour
      1. USJanus Troelsen
    2. COI'm been abusing the WS all day and it seems like it is not clearing up any memory or resources the initial memory starts at about 25MB and is currently @ 53MB. I got it to slow down from being an instant call back to about 3-5 seconds, but then the number of handles went from 1200 to 900 and it was quick again. It seems like the WS is never cleaning itself up, and causing issues. Is there something I should do programmaticly in order to trigger this after the request is over? Or is there something else I should be looking for?
      singulars
      1. POWeb Service dying after an hour
      1. USJohn
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload