Reputation: 6440
We have a performance measurement module that relies on HttpModule and HttpHandlers and works like this:
This process works fine for most cases, but there are some instances that report network time in excess of an hour! This indicates a very large passage of time between the the writing of end time and firing off the AJAX request or a large passage of time between firing off AJAX request and the time it gets to the app server. I am trying to figure what could be causing this issues in the wild. Why does the operation not simply time out?
Upvotes: 0
Views: 591
Reputation: 7480
Extend your troubleshooting: append values to the IIS log (HttpContext.Current.Response.AppendToLog(string)).
The IIS log will show your entries and you can determine when those requests were actually recorded. You can append whatever you want and it shows up in the query field of the log (assuming you're using W3C format.)
If you're experiencing delays in requests, as the evidence suggests, you can verify it. This will give you the IIS log as a comparative source against the recorded values in cookies.
Upvotes: 1
Reputation: 532555
Are you including some unique id that allows the AJAX request handler to figure out the which end time to use for the calculation? If not, perhaps enough of the page has been rendered on the client that the AJAX request is actually coming before the end time has been written to the database and it is using the wrong end time.
Upvotes: 0