0

A high volume classic ASP page is using an ASP.NET page to return xml data, taking advantage of .NET caching capabilities. The cache being used in the .net page is the Context Cache. Recently after 1 year of running smoothly - IIS7 starts responding with a 503 unavailable and in the HTTP.sys error log it displays a few connection_dropped events, then a slew of connection_dropped_list_full events. At this point the servers is unavailable.

Looking at possibilities of having hit a cache limitation or a network problem.

Diego
  • 37
  • 5
  • I have no idea how you could expect anyone to solve the problem for you. _You_ have access to the code, but we do not. – John Saunders May 03 '12 at 03:59
  • Question states that this has been running for 1 year without an issue, no code changes have been made and I am really looking to see if anyone has come across the connection dropped list full error in IIS and what they have attributed it to. As for the code, it's nothing complicated - a context.cache.insert is being used when the object is created from a db call. – Diego May 03 '12 at 04:59
  • That is indeed what I was looking for when asking this question - that someone had a similar set up and had seen this issue. Nevertheless there is enough lack of information on the web regarding this condition that we will open a ticket with MS. – Diego May 03 '12 at 19:32
  • Did you ever solve this? – matt-dot-net Jun 08 '16 at 19:41

0 Answers0