Exception "Thread was being aborted." with Server.Transfer()

[Totto]

Hi,
I'm doing a server.transfer from a click event of a button,
but an exception is raised with "Thread was being aborted"

Anyone know why?

Thanks Tor

 

[Laurent Bugnion]

Hi,

Hi,
I'm doing a server.transfer from a click event of a button,
but an exception is raised with "Thread was being aborted"

Anyone know why?

Thanks Tor

This exception is thrown by the system when a redirection occurs. There
is nothing you can do against it. You must catch it (using try/catch),
but note that the exception is propagated even if you catch it in the
lower layers of your system.

"Transfer calls End, which throws a ThreadAbortException exception upon
completion."

http://msdn2.microsoft.com/en-us/library/y4k58xk7.aspx

"ThreadAbortException is a special exception that can be caught, but it
will automatically be raised again at the end of the catch block."

http://msdn2.microsoft.com/en-us/library/system.threading.threadabortexception.aspx

HTH,
Laurent

 

[Guest]

Totto,

This happens because it calls 'Response.End' internally.

check out http://support.microsoft.com/default.aspx?scid=kb;en-us;312629

Regards,
Augustin
http://augustinprasanna.blogspot.com

 

[Kevin Jones]

I'm doing a server.transfer from a click event of a button,

> but an exception is raised with "Thread was being aborted"

When you do a Server.Transfer, you are saying to ASP.Net, "end the
processing of the current page and transfer control to the new page, and
don't come back to the current page when you are finished!"

To do that ASP.Net causes an exception on the current thread, that will
end the processing of the current page. You can't stop this exception
and you don't need to handle it.

Where are you seeing the exception?

Kevin

 

[Juan T. Llibre]

http://support.microsoft.com/kb/312629/EN-US

....recommends using Server.Execute, instead of Server.Transfer,
to work around that problem.