Topic: Thread was being aborted
All greetings! Sometimes successively (once a month, but recently couple of days was), in service process.Net arises error ThreadAbortException (message Thread was being aborted). Judging by the description in MSDN - such error is possible if to a flow explicitly told Abort, but in our code such is not present (used libraries also it is possible to eliminate). Why then arises??? Very strange. From details: in all cases, the error happened in different places of our code which was fulfilled from Task. Also during such moments much Task could be launched and high CPU loading. But if thus the torn off operation then to restart, , that is matter is not in the most executable to procedure. In the stack anything interesting (our code) which suddenly in the arbitrary place is interrupted with such error. A host is IIS, and it happens at web application start, are launched that certain initialization, but not necessary was asynchronously fulfilled at once. In flow of the subsequent operation such . It is exact not domain outswapping ( the domain only rose also remaining starting continue operation). It is exact not in the course of http-inquiry handling, i.e. not because of possible redirects. Somebody faced a similar problem? Where to dig?... upd - the answer was business it appeared in the following. Before start of planned asynchronous initialization, had time to arrive http-rekvest and initialization went synchronously in a flow of it . The request was on the asynchronous controler (mvc3) which had AsyncTimeout. initialization went long transited and asp.net is visible a worker thread (about what in an event-broad gull and there was a message second in a second coincided with already our broad gull about an error).