This was happening to me as well, and I discovered that ASP.NET was throwing this exception whenever I made a call to Response.Redirect( "", true ). The boolean tells it to cancel any current output - this seemed to be where the exception was coming from.
Hope this helps, cl. -----Original Message----- From: Mark Vatsaas [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 8:25 PM To: [EMAIL PROTECTED] Subject: [ADVANCED-DOTNET] Strange exception I have a web service that uses an object on an application tier through .NET remoting. Occasionally, I am getting the following exception when attempting to create the remoted object: System.Threading.ThreadAbortException Message: Thread was being aborted. When it happens, there is absolutely no network traffic sent out of the web server to the app server. Whatever it is doing, it dies before it hits the network, so this isn't related to the listener. Subsequent calls succeed, though nothing has changed as far as I can tell. Anybody have any idea what this exception means and what I can do about it? You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
