Comments on: Long running method

By: Anonymous

Anonymous — Sun, 31 Jul 2005 22:13:42 +0000

It was taking 50 seconds to connect to MySql 4.1.x from my windows 2003 machine, heres what fixed it.

By: breichelt

breichelt — Sun, 24 Jul 2005 08:17:27 +0000

So, I found the problem, the issue was that I was calling into an api that used the HttpContext.Current, not just the Request object that I was passing in, and by the time came to call HttpContext.Current, I was getting a NullReferenceException thrown because there was no HttpContext, like Scott mentioned.

However, I fixed the problem by discovering why the method was taking a long time (6 minutes) in the first place, but I’ll post that as another entry. But now I dont need to run the method asynchronously, so its a non issue, thanks for the suggestions.

By: btompkins

btompkins — Fri, 22 Jul 2005 08:05:04 +0000

I am actually just getting into this this week… have you read this? It’s an oldie, but goodie.

http://msdn.microsoft.com/msdnmag/issues/03/06/Threading/default.aspx?print=true

By: breichelt

breichelt — Fri, 22 Jul 2005 07:58:14 +0000

Geoff, I also tried explicitly creating a new thread, but I got the same result. I think Scott is correct in his assertion, so I’m going to try Thomas’s suggestion, its a pain in the to grab everything that I want from the Request, but such is life…….

By: Anonymous

Anonymous — Fri, 22 Jul 2005 06:52:47 +0000

I think the safest approach would be to extract everything you need from the request and pass the extracted data to the thing you add to the thread pool.

I believe there is always a risk that the request will end before you access it.

By: Anonymous

Anonymous — Thu, 21 Jul 2005 22:47:17 +0000

Geoff is right. The thread inside of Page_Load will queue the work item for processing, then run off and finish rendering the page.

When the ASP.NET runtime sees the request has finished processing, then all bets are off on any state related to the request. That includes Request, Response, and any other property on HttpContext.

By: gappleby

gappleby — Thu, 21 Jul 2005 21:48:49 +0000

I’d say what’s happening is that the queued workitem never gets a chance to run before the page is finished and has been unloaded.

Without trying it out, I can’t say for sure what’s going on, but as a quick test, try explicitly creating a new thread and kicking it off, instead of adding it to the threadpool. There’s more liklihood that the thread will at least start up before your page finishes.

If it _does_ start up, then you at least know why this method fails, if not the right way to do it

By: breichelt

breichelt — Thu, 21 Jul 2005 20:07:30 +0000

Kirk, this is just some sample code, the actual code had other stuff in it that I removed for clarity and brevity, the other code was irrelevant.

By: Anonymous

Anonymous — Thu, 21 Jul 2005 19:22:54 +0000

not sure if this affects anything, but you’d probably want to wrap that code inside a “if (!Page.IsPostback) {…}” block, so you can guarantee it’s only executed the first time.