-
Notifications
You must be signed in to change notification settings - Fork 61
404's logged multiple times #167
Comments
Correction; the 44 repeated log entries isn't consistent - it changes, always in the order of "tens" of entries. Suspect this may be retry handling in the DatabaseContext perhaps (we're using Azure SQL)? |
@PhilDye I can confirm 404s are being logged multiple times for me as well. However, it's only logging each 404 3 times. In the meantime, if it is the same URL, you could potentially add it to the ignore list |
@PhilDye I've a suspicion I know what's going on here. Would you mind telling me how many times the following is in your log file please? "UrlTracker HttpModule | Subscribed to AcquireRequestState and EndRequest events" |
@daniel-chenery We'll need to turn up the logging; this site is now in production, so not running at INFO level currently... // @michaelchart |
@PhilDye If it's not doable, then no worries :) I've a suspicion it's down the the Modules being registered multiple times. I can only assume, Azure, being Shared Hosting has more AppPools, and therefore loads it an excessive amount of times. |
@PhilDye Would you mind giving the latest BETA version and spin and see if this fixes it for you? :) |
Running this locally first, I'm seeing every log entry (at least) duplicated, but even allowing for that, multiple On the plus side, I do see each 404 getting inserted to the db only once, from some simple tests. |
Is the duplicate |
Yupp :) If I pop that in the lock, it causes an (apparently) unknown YSOD. Thanks for the merge, I'll take a look shortly! :) |
v3.13.1 from nuget
We're seeing each genuine 404 request (ie falling right through, with no redirect) being logged 44 times. This is adding significant subsequent rows for subsequent queries to search, and hitting performance hard, especially as we've just launched it in a new site, that is generating significant 404's.
Possibly related to #166 ?
The text was updated successfully, but these errors were encountered: