>Hope it helps out. Anytime you change code, you risk changing the conditions and then the error not happening. Changing configuration this way should have less impact.

Yes, but I am catching up the ASP.NET events right now and this is already there. This will give me a confirmation on which event takes a long time to response. I also added a few of them at various locations with the milliseconds time stamp so if it is in the code, for an unknown reason, I will be able to know as well. But, so far, it seems that if IIS is not sollicitated for a long period, it would have some kind of impact of processing a hit as it arrives and creating a queue to them let several hits to be released in the same second.

IAC, what you mentioned is a good approach. It is just that I need to log additional things presently that this approach wouldn't let me to do.

Once I find the location, I will be able to remove all that and apply this approach instead. I just need to make sure this is happening between two ASP.NET events.