Question

Hi,

I try to fix issues with deadlocks. And I see that you have some trick in Global.asax.cs for reprocessing of error (TryToReprocessRequest). Possibly it could help me but unfortunately it doesn't work.

Error is raised during processing of request. HttpRuntime.ProcessRequest(wr); "Operation is not valid due to the current state of the object."

Environment: WindowsServer 2003, IIS6

Do you know the reason?

Accepted Answer

2

Likely, this happens because ASP.NET was changed after the moment we wrote this code.

TryToReprocessRequest actually makes a hack by pushing request back to ASP.NET processing pipeline. As you see, this hack doesn't work now.

Possible workaround (I didn't try it) is to try setting _endOfRequestCallback of appropriate object (ISAPIWorkerRequest, but you must find the path to that instance) to null before ProcessRequest invocation. Of course, using reflection.

answered Oct 22 '10 at 11:18

Alex Yakunin
2971●4●4●12

1

Great! Your workaround works...at least for IIS 6.. I'll post source of changed TryToReprocessRequest method on Monday. Спасибо за помощь :)

(Oct 22 '10 at 12:20) Denis

Greetings! Thanks god I still remember such stuff from v3.X ;)

(Oct 22 '10 at 13:13) Alex Yakunin

Answer 2

It seems that I found acceptable solution for my project. Probably that could help to someone else too.

So I added processing of deadlocks in Global.asax.cs Application_Error handler. And in case of exception I just make a Response.Redirect


protected virtual void Application_Error(object sender, EventArgs e)
        {               
                Exception ex = Server.GetLastError().InnerException;
                if (ex is DeadlockException || ex is TransactionIsLockedException)
                {                   HttpContext.Current.Response.Redirect(Request.RawUrl.ToString());
                }
}

Subscription:

Related questions