ThreadAbortException

StrataFrame Forum

Back

ThreadAbortException

Author	Message
Larry Caylor	Larry Caylor posted 7 Years Ago Topic Details Share Topic
Group: Awaiting Activation Posts: 592, Visits: 3.7K	HI Ben, My ES has started spitting out a lot of "Thread was being aborted." alerts. Details: ThreadAbortException Thread was being aborted. Source : MicroFour StrataFrame Enterprise Server Stack Trace: atMicroFour.StrataFrame.Enterprise.Server.RemoteDataSource.ProcessRequest(HttpContextcontext) It's happening on multiple clients. Any suggestions on what to look for in troubleshooting this? -Larry
	Reply Like 2
StrataFrame Team	S StrataFrame Team posted 7 Years Ago Post Details Share Post
S Group: StrataFrame Developers Posts: 3K, Visits: 2.5K	Are your clients experiencing the issues? Or are the reports coming in with random IP addresses from places like Russia or China? Also, we don't abort any threads in the ES, so it could be that your application pool is getting recycled. You might check the IIS logs and see if there are any messages about it there.
	Reply Like 1
Larry Caylor	Larry Caylor posted 7 Years Ago Post Details Share Post
Group: Awaiting Activation Posts: 592, Visits: 3.7K	The issue is being seen by clients on my network. All of the ES error messages contain internal IP addresses. I took a look at the server application log and found some ASP.NET 2.0 warnings Event code: 3001 Event message: The request has been aborted. Event time: 5/16/2017 2:02:44 PM Event time (UTC): 5/16/2017 9:02:44 PM Event ID: 1e61edd185584442a086aef316b599de Event sequence: 3124190 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT-1-131394112699117893 Trust level: Full Application Virtual Path: / Application Path: C:\inetpub\StrataFrameES\ Machine name: HSDSFES Process information: Process ID: 1032 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: HttpException Exception message: Request timed out. Request information: Request URL: <Removed before posting> Request path: /RemoteDataSource.ashx User host address: 172.21.12.34 User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 33 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace:
	Reply Like 3
StrataFrame Team	S StrataFrame Team posted 7 Years Ago Post Details Share Post
S Group: StrataFrame Developers Posts: 3K, Visits: 2.5K	Hrm. Those HttpException messages with "request timed out" will cause a thread abort. When the server thinks the request is taking too long, it will kill the thread that's working. Do you know if your users are getting it in a specific place in the application? Is there a query that's starting to take too long to run? Maybe the database size is becoming a factor as it grows? Many, many questions.
	Reply Like 1
Larry Caylor	Larry Caylor posted 7 Years Ago Post Details Share Post
Group: Awaiting Activation Posts: 592, Visits: 3.7K	I can't pin it on any singe query. I had my DBA take a look at the SQL and he couldn't see any performance issues there. But just to clarify, is the timeout related to traffic between the ES server and the SQL box or could it possibly be an issue between the ES server and the client? Also what does the transaction timeout in the ES data source configuration do? How is it related to the SQL command timeout?
	Reply Like 3