Showing results for 
Show  only  | Search instead for 
Did you mean: 

Why do .Net requests run longer than executionTimeout allows?



I'm looking at long running requests in my .net application and wondering why they run over the default timeout of 110 seconds. I've seen requests that run upwards of 177 seconds.

I would expect the request to be terminated and resources to be reallocated if it went beyond the timeout.

In googling for the answer I came across this posting which suggests that the iis server logs include network time. Does Dynatrace get its response time from the server logs (I doubt it since its instrumented code).

Thank you


Dynatrace Leader
Dynatrace Leader

The times will come from how long it was between the method invocation and when the method execution completes. For the simple example of a web request it is when that request is made to when the response is returned.

I am not familiar with this area but looking at that link it appears that the log field may be calculated in a similar way (when the client awknowledges the last response packet):

"Before HTTP.sys logs the value in the time-taken field, HTTP.sys usually waits for the client to acknowledge the last response packet send operation or HTTP.sys waits for the client to reset the underlying TCP connection. Therefore, when a large response or large responses are sent to a client over a slow network connection, the value of the time-taken field may be more than expected."

So I would think it is not using the log to determine the time, but rather both times are just determined based on a similar criteria.

This link might have some useful stuff around the PurePath details: