Pregnant Man » An interesting fusion cache lock: that???s what the GAC is meant for

Mon, 23 Jun 2008 18:51:39 GMT

PingBack from http://wordnew.acne-reveiw.info/?p=2029

re: An interesting fusion cache lock: that’s what the GAC is meant for

Roberto Santoro — Thu, 02 Oct 2008 16:51:19 GMT

Hello,

I found this article very interesting, I think I'm going through a similar problem but my worker process crashes rather than hang.

I'm relatively new to dump analysis and I'm stuck, may I ask you for your opinion?

Here is the stack:

0f21f36c 02f9b090 System.ArgumentOutOfRangeException

0f21f3b8 02f9b090 System.ArgumentOutOfRangeException

0f21f3c8 06bef6e4 System.String currentUser

0f21f3cc 02f9a2c8 System.Collections.ArrayList

0f21f3d0 02f99ac0 System.Web.SessionState.HttpSessionState

0f21f3e0 02f99ac0 System.Web.SessionState.HttpSessionState

0f21f3ec 06bef6e4 System.String currentUser

0f21f3fc 02f9b090 System.ArgumentOutOfRangeException

0f21f404 02f9a2c8 System.Collections.ArrayList

0f21f40c 02f99ac0 System.Web.SessionState.HttpSessionState

0f21f460 02f9b090 System.ArgumentOutOfRangeException

0f21f47c 02f9b090 System.ArgumentOutOfRangeException

0f21f480 02c76fa4 System.String index

0f21f48c 06c005a4 ASP.global_asax

0f21f494 06c03864 System.Web.SessionState.SessionStateModule

0f21f4a4 06c03864 System.Web.SessionState.SessionStateModule

0f21f4b0 06c03864 System.Web.SessionState.SessionStateModule

0f21f4b4 02c12e74 System.EventArgs

0f21f4c0 02c12e74 System.EventArgs

0f21f4c8 06c03864 System.Web.SessionState.SessionStateModule

0f21f4d4 06c03864 System.Web.SessionState.SessionStateModule

0f21f4dc 02f73d94 System.Web.HttpContext

0f21f500 06c03864 System.Web.SessionState.SessionStateModule

0f21f508 06c03864 System.Web.SessionState.SessionStateModule

0f21f524 02f73d94 System.Web.HttpContext

0f21f528 06c057e4 System.Web.BeginEventHandler

0f21f52c 06c09f90 System.Web.HttpApplication+AsyncEventExecutionStep

0f21f530 06c005a4 ASP.global_asax

0f21f534 06c005a4 ASP.global_asax

0f21f540 06c09fb4 System.AsyncCallback

0f21f544 02c12e74 System.EventArgs

0f21f54c 06bd8be0 System.AsyncCallback

0f21f550 06c005a4 ASP.global_asax

0f21f568 06c09f90 System.Web.HttpApplication+AsyncEventExecutionStep

0f21f56c 06c005a4 ASP.global_asax

0f21f570 06bd8988 System.Web.RequestTimeoutManager

0f21f580 02f740c0 System.Web.HttpApplication+ThreadContext

0f21f584 06bd8be0 System.AsyncCallback

0f21f588 06c005a4 ASP.global_asax

0f21f59c 06c005a4 ASP.global_asax

0f21f5a0 02f740a0 System.Web.AspNetSynchronizationContext

0f21f5a4 02f740c0 System.Web.HttpApplication+ThreadContext

0f21f5a8 02f73d94 System.Web.HttpContext

0f21f5ac 06c005a4 ASP.global_asax

0f21f5b4 06c09568 System.Web.HttpApplication+ApplicationStepManager

0f21f5d8 06bd8be0 System.AsyncCallback

0f21f5dc 02f74080 System.Web.HttpAsyncResult

0f21f5e0 06c005a4 ASP.global_asax

0f21f5e4 02f73d94 System.Web.HttpContext

0f21f5f0 02f738a0 System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6

0f21f5f4 06c005a4 ASP.global_asax

0f21f5f8 02f73fe8 System.Web.HttpWriter

0f21f600 02f73d94 System.Web.HttpContext

0f21f604 06bd8be0 System.AsyncCallback

0f21f608 02f73d94 System.Web.HttpContext

0f21f60c 02f738a0 System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6

0f21f610 06bd88d4 System.Web.HttpRuntime

0f21f62c 02f738a0 System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6

0f21f63c 06bc1a70 System.String D:\MyWebsite\www.mywebsite.com\

0f21f640 02f73a88 System.String D:\MyWebsite\www.mywebsite.com\

0f21f67c 02f738a0 System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6

0f21f680 02bfc304 System.Web.Hosting.ISAPIRuntime

0f21f6c0 02bfc304 System.Web.Hosting.ISAPIRuntime

0f21f814 02f6bf0c System.Threading.ExecutionContext

0f21f81c 02c1d27c System.Threading._TimerCallback

0f21f830 02c1d27c System.Threading._TimerCallback

0f21f834 02f6bf0c System.Threading.ExecutionContext

I think the problem is with the arguments sent to ASP.global_asax being "out of range" (I checked the values m_paramName and m_actualValue for System.ArgumentOutOfRangeException and they are "index" and 0).

I am trying to understand what should be my next step, how can I understand who's making that call with wrong arguments?

Thanks a lot,

Roberto.

re: An interesting fusion cache lock: that’s what the GAC is meant for

Carlo Cardella — Fri, 03 Oct 2008 17:50:56 GMT

Roberto, that seems to be the output of a !dumpstackobjects command, correct? If you use !clrstack you'll get more detailed information about the managed stack.

Apart from that, it's really hard to tell what's going wrong without having the change to look at a read dump... Have you considered opening a call with Microsoft Support? From your name I guess you're Italian (or maybe Spanish), are you? Either me or my colleagues will be happy to assist you on this matter.

HTH

re: An interesting fusion cache lock: that’s what the GAC is meant for

Roberto Santoro — Thu, 20 Nov 2008 16:26:48 GMT

Hey Carlo,

I hadn't noticed your name, I'm italian and I used to work for the MSPSS in Dublin.

I was thinking of opening a case with microsoft but I would have liked to solve this one on my own, you guys make it too easy.

I'll keep trying if I don't manage I'll give you a call.

Bye,

Roberto Santoro.

P.S.: do you have any interesting reading about IIS dump analysis (for dummies)?

re: An interesting fusion cache lock: that’s what the GAC is meant for

Carlo Cardella — Fri, 21 Nov 2008 10:34:41 GMT

Hi Roberto,

For dump analysis I can suggest to have a look at my blogroll where you can find blogs on debugging from some of my colleagues (Tess, Doug, Johan, Tom and the others) and some interesting sites as well.

Speaking of books, I read "Advanced Windows Debugging" and "Debugging Applications for Microsoft .NET and Microsoft Windows" which are good and useful, plus I've heard of "Memory Dump Analysis Anthology" (two volumes) but I have not read them myself.

HTH