Getting an unhandled exception, but unable to catch with try...catch

I get this error in the browser:

Code:

---

Thread was being aborted.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Threading.ThreadAbortException: Thread was being aborted.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ThreadAbortException: Thread was being aborted.]
  System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +486
  System.Web.ApplicationStepManager.ResumeSteps(Exception error) +501
  System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +123
  System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +379


Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053

---

I have try{}catch(Exception ex){} in the right place:

Code:

---

protected void Button1_Click(object sender, EventArgs e)
        {
try
{
// all processing occurs inside here
}
catch(Exception ex)
{

}
}

---

I even created a global.asax file and on the Application_Error event, I wrote a code that would email me the error (and i'm not getting an email regarding that error when I get the error shown above). I know for a fact that the thread is going inside the "try" statement because I send emails to myself whenever it finishes certain codes inside of it. So how come I'm getting that error in my browser instead of it being handled in my "catch" statement? I have two problems here, one, why is the exception not going to my "catch" statement, and two, why am I getting that error in the first place.

Note: my web app calls a webservice.

correction, it is being caught. But other than Response.Close and Response.Redirect(), what else could cause a thread abortion exception? because I am not calling any of those two.

Edit: My web app does a pretty long process (about 2-3 minutes) before it sends the response back. Could it be the idle timeout? I checked my IIS 6.0 and it is currently at idleTimeout=20 (minutes). So i doubt it could be that.

benmartin101,

Am I right in saying that this is the same problem as in your other thread? If so, can I ask that you limit questions to only one thread, otherwise the forums can become messy.

Thanks

Gary