If you are an administrator, you may receive this email from time to time.

Thread was being aborted.   at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)
  at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
  at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
  at d.a()
  at d.b(Int32 A_0)<br>
<br>

IIS shutdowns an application after a certain period of idle. nService has background task that wakes up every minute to handle sending email, receiving email and periodical events. IIS only looks at visitor activity from the web. It is not aware of nService's background task. When IIS shuts down nServier while nService's background task is doing it is work, this type of error results.

To fix the problem, you can running IIS manager, expand the Application Pools node on the left, select the Advanced Settings of the IIS application pool that runs nService, and set the idle time-out and the recycling regular time interval to 0.

idle timeout
Article #414
Attachments:
timeout.png (40519 bytes)
Keywords:
nService Thread was being aborted
Updated On: 1/26/2011 Index
Was this article helpful? Yes | No