Quantcast
Channel: Troubleshooting
Viewing all articles
Browse latest Browse all 1814

Failed request tracing bug

$
0
0

Hi,

I believe i found a bug.

I configured FRT to log any requests longer then x seconds for Classic ASP requests.

Inside the log under "request summery" => "time taken" i can see that indeed that request took this long.

But in "request details" under "complete request trace" or "performance view" i can't find anything that would explain this duration as all records are at "0ms".

Then i looked at the last record of the "Complete request trace" and saw that it's a "ASP_SCRIPT_TRACE_COM_CALL_START" which is accessing the DB. since the "ASP_SCRIPT_TRACE_COM_CALL_END" that should follow that one is missing, the time of that db access is not logged anywhere in the report.

I have found this issue in multiple trace logs where the log ends with a DB request. And also, that DB request is doubled in the log for some reason. When the first group of "START" and "END" show "0ms".

See example image: https://drive.google.com/open?id=0BwoJABE2FogsZjVYUkVKNUFBLXM


Viewing all articles
Browse latest Browse all 1814

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>