By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,672 Members | 1,628 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,672 IT Pros & Developers. It's quick & easy.

Server.Execute generates "Thread was being aborted"

P: n/a
Hi,

Long story short, we use "Server.Execute" to grab the output from an
ASPX page ...

Server.Execute("page.aspx", textWriter);

We've noticed that intermittantly, we get a "Thread was being aborted"
error when this method is called.

Anyone any ideas where to start looking?
Is this likely to be caused by a problem in the "page.aspx"?
Thanks for any help
Meil
Oct 11 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Possibly, it's difficult to say without seeing code.

--
Regards,
Alvin Bruney

Want a free copy of VS 2008 w/ MSDN premium subscription?
Details at http://msmvps.com/blogs/alvin/Default.aspx

Auther Plug
OWC Blackbook now on download at www.lulu.com/owc

"Neil" <gi*******@gmail.comwrote in message
news:e4**********************************@p59g2000 hsd.googlegroups.com...
Hi,

Long story short, we use "Server.Execute" to grab the output from an
ASPX page ...

Server.Execute("page.aspx", textWriter);

We've noticed that intermittantly, we get a "Thread was being aborted"
error when this method is called.

Anyone any ideas where to start looking?
Is this likely to be caused by a problem in the "page.aspx"?
Thanks for any help
Meil
Oct 11 '08 #2

P: n/a
most likely the page is doing a redirect, which will cause this error.

-- bruce (sqlwork.com)

Neil wrote:
Hi,

Long story short, we use "Server.Execute" to grab the output from an
ASPX page ...

Server.Execute("page.aspx", textWriter);

We've noticed that intermittantly, we get a "Thread was being aborted"
error when this method is called.

Anyone any ideas where to start looking?
Is this likely to be caused by a problem in the "page.aspx"?
Thanks for any help
Meil
Oct 11 '08 #3

P: n/a
My guess would be that page.aspx makes a call to Response.End or
Response.Redirect

George.

"Neil" <gi*******@gmail.comwrote in message
news:e4**********************************@p59g2000 hsd.googlegroups.com...
Hi,

Long story short, we use "Server.Execute" to grab the output from an
ASPX page ...

Server.Execute("page.aspx", textWriter);

We've noticed that intermittantly, we get a "Thread was being aborted"
error when this method is called.

Anyone any ideas where to start looking?
Is this likely to be caused by a problem in the "page.aspx"?
Thanks for any help
Meil
Oct 11 '08 #4

P: n/a
I've a stack trace from catching the exception when "Server.Execute"
is called:

at System.Web.HttpContext.InvokeCancellableCallback(W aitCallback
callback, Object state)
at System.Web.UI.Page.AsyncPageBeginProcessRequest(Ht tpContext
context, AsyncCallback callback, Object extraData)
at ASP.range_rx_index_aspx.BeginProcessRequest(HttpCo ntext context,
AsyncCallback cb, Object data)
at System.Web.HttpServerUtility.ExecuteInternal(IHttp Handler
handler, TextWriter writer, Boolean preserveForm, Boolean
setPreviousPage, VirtualPath path, VirtualPath filePath, String
physPath, Exception error, String queryStringOverride)
at System.Web.HttpServerUtility.Execute(String path, TextWriter
writer, Boolean preserveForm)
at System.Web.HttpServerUtility.Execute(String path, TextWriter
writer)
at HttpProxy.ExecuteLocal(String url, Dictionary`2
queryStringVariables, Boolean keepOriginalVariables, Boolean cachable)
at HttpProxy.ExecuteLocal(String url, Boolean cachable)
at RetrieveContent.CallHttpProxy()
at RetrieveContent.RefreshContent()
at ASP.range_index_aspx.RenderContent(Boolean fromHistory)

I've looked at the page in question, "range_rx_index_aspx", but
haven't found any obvious "Response.Redirect" or "Response.End".
Anyone any advice on how to track this one down?

Cheers
Neil
Oct 12 '08 #5

P: n/a
On 12 Oct, 16:55, Neil <gibbon...@gmail.comwrote:
I've a stack trace from catching the exception when "Server.Execute"
is called:

* at System.Web.HttpContext.InvokeCancellableCallback(W aitCallback
callback, Object state)
* at System.Web.UI.Page.AsyncPageBeginProcessRequest(Ht tpContext
context, AsyncCallback callback, Object extraData)
* at ASP.range_rx_index_aspx.BeginProcessRequest(HttpCo ntext context,
AsyncCallback cb, Object data)
* at System.Web.HttpServerUtility.ExecuteInternal(IHttp Handler
handler, TextWriter writer, Boolean preserveForm, Boolean
setPreviousPage, VirtualPath path, VirtualPath filePath, String
physPath, Exception error, String queryStringOverride)
* at System.Web.HttpServerUtility.Execute(String path, TextWriter
writer, Boolean preserveForm)
* at System.Web.HttpServerUtility.Execute(String path, TextWriter
writer)
* at HttpProxy.ExecuteLocal(String url, Dictionary`2
queryStringVariables, Boolean keepOriginalVariables, Boolean cachable)
* at HttpProxy.ExecuteLocal(String url, Boolean cachable)
* at RetrieveContent.CallHttpProxy()
* at RetrieveContent.RefreshContent()
* at ASP.range_index_aspx.RenderContent(Boolean fromHistory)

I've looked at the page in question, "range_rx_index_aspx", but
haven't found any obvious "Response.Redirect" or "Response.End".
Anyone any advice on how to track this one down?

Cheers

Neil
Noticed that the page being executed is missing a image, which
generates a 404, which is being handled by our custom 404 page. Could
this be the cause of the aborted thread?

Cheers
Neil
Oct 12 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.