Exception and Excessive CPU Usage on Automatic AgilePoint Application Pool Recycle

Description

The following error appears in the application log on DW20.exe (windows error reporting) which starts up and causes excessive CPU each time the AgilePoint application pool does an automatic recycle.

ID 1334An unhandled exception occurred and the 
process was terminated. 
Application ID: /LM/W3SVC/[ID]/ROOT/AgilePointServer 
Process ID: 68692 Exception: System.Threading.ThreadInterruptedException 
Message: Thread was interrupted from a waiting state. 
StackTrace: at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout) 
at System.Threading.Thread.Sleep(TimeSpan timeout) 
at Ascentn.SharePoint.ContentListener.Process.RunThread() 
at System.Threading.ThreadHelper.ThreadStart_Context(Object state) 
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, 
ContextCallback callback, Object state) 
at System.Threading.ThreadHelper.ThreadStart

The thread interruption is caused by the recycle.

Applies To

AgilePoint Server

Resolution

To avoid interruption of service or excessive CPU usage due to AgilePoint reload at startup, schedule the recycle during off-peak hours. In IIS, configure the AgilePoint Server application pool properties to schedule Application Pool recycling at a time that will minimally impact your company's operations.