Thread was being aborted

Question

I am using Server.Transfer. Everything works fine, but exception log shows following exception.

System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at System.Web.HttpServerUtility.Transfer(String path)

Any idea to avoid above exception.

score 41 · Accepted Answer · answered Sep 16 '09 at 14:49

This exception is throw by the call to Server.Transfer in order to halt the execution of the current method - exactly the same thing gets thrown if you do Response.Redirect.

The two choices you have are:

Catch and rethrow the ThreadAbortException / reperform the Server.Transfer
Make sure that you only do Server.Transfer in places where it wont be caught (recommended)

EDIT: Scratch that, http://support.microsoft.com/kb/312629 has a couple of other suggestions to try, but I still recommend #2 above.

score 11 · Answer 2 · answered Jan 15 '13 at 08:02

11

Another way to solve this, is to catch the generated error and to not rethrow it:

        catch (ThreadAbortException)
        { 
        }

answered Jan 15 '13 at 08:02

Chris Ghysbrecht

111
1
3

1

empty catches are ***bad*** – Rob May 12 '15 at 06:16
7

@Rob, usually, but not always. – Holf Oct 09 '15 at 10:27

Jayesh Sorathia · Answer 3 · 2013-01-17T10:20:06.230

8

This problem occurs in the Response.Redirect and Server.Transfer methods because both methods call Response.End internally.

Solution for this Problem is as follows.

For Server.Transfer, use the Server.Execute method instead.

Visit this link for download sample example. http://jayeshsorathia.blogspot.com/2012/03/thread-was-being-aborted-error-occured.html

edited Jan 17 '13 at 10:20

answered Apr 23 '12 at 09:52

Jayesh Sorathia

1,558
15
15

score 8 · Answer 4 · edited Oct 16 '12 at 11:13

8

Caling Server.Transfer will call Response.End which always throws a ThreadAbortException. This is a "special" exception because while it can be caught in a catch block, it will always be re thrown at the end of the catch block. I would have your error logging ignore ThreadAbortExceptions.

edited Oct 16 '12 at 11:13

Ian Kemp

26,561
17
107
129

answered Sep 16 '09 at 14:50

Matt Wrock

6,502
28
23

It make sense to me that Server.Transfer will call Response.End implicitly. What do you mean by error logging ignore threadAbortException. – Syed Tayyab Ali Sep 16 '09 at 14:54
4

If you are logging exceptions to a persistable logging system, I would filter out ThreadAbortExceptions or have your reports that query this loging system filter them out. – Matt Wrock Sep 16 '09 at 15:02
It make sense that this exception is not serious one, therefore I can ignore it by filtering out.. thank you. – Syed Tayyab Ali Sep 16 '09 at 15:11

score 1 · Answer 5 · edited Feb 11 '17 at 12:29

1

Replace Response.End() With HttpContext.Current.ApplicationInstance.CompleteRequest();

edited Feb 11 '17 at 12:29

Tunaki

125,519
44
317
399

answered Feb 11 '17 at 12:24

Zuhair Ali

21
6

score 0 · Answer 6 · edited May 23 '17 at 11:33

0

Replacing Response.End() by the following helped fix the problem.

Response.Flush(); Response.Close();

Refer Can we use Response.Flush () instead of Response.End()

edited May 23 '17 at 11:33

Community

1
1

answered Aug 11 '16 at 18:15

user6706374

1
1

Thread was being aborted

6 Answers6

Linked