What are some best practices for managing background threads in IIS?
I have written an HttpModule that spawns a background thread. I’m using the thread like a Scheduled Task that runs in-process, which is really handy.
multithreading
How do you handle a thread that has a hung call?
I have a thread that goes out and attempts to make a connection. In the thread, I make a call to a third party library. Sometimes, this call hangs, and never returns. On the UI thread, I want to be able to cancel the connection attempt by aborting the thread, which should abort the hung call to the third party library.
Why Thread.Sleep() is so CPU intensive?
I have an ASP.NET page with this pseduo code:
Will a request in IIS run on a single thread?
We have a system that runs in IIS.
Thread was being aborted
I am using Server.Transfer. Everything works fine, but exception log shows following exception.
Does async and await increase performance of an ASP.Net application
I recently read an article about c#-5 and new & nice asynchronous programming features . I see it works greate in windows application. The question came to me is if this feature can increase ASP.Net performance?
REST WCF service locks thread when called using AJAX in an ASP.Net site
I have a WCF REST service consumed in an ASP.Net site, from a page, using AJAX.
Why ASP.NET kills my background thread?
I have the following code in my codebehind (aspx.cs):
How to properly make asynchronous / parallel database calls
I’m looking for the proper way to handle multiple database calls that would likely benefit from running simultaneously. The queries are just to stored procedures that are either doing inserts or merges using data that is programmatically assembled into DataTables in my ASP.NET MVC app.
Best way to run a background task in ASP.Net web app and also get feedback?
I am thinking on the following approach but not sure if its the best way out: