Hello team!
We having performance issue when working with net api.
When Avaya.ApplicationEnablement.DMCC.ServiceProvider class instance created, it also starts additional thread with FileSystemWatcher
in it, to react for DMCC.config file changes, even if there are no such file.
After some time there are couple thousand threads can be created, all with such call stack:
DomainBoundILStubClass.IL_STUB_PInvoke(Microsoft.Win32.SafeHandles.SafeFileHandle, System.Runtime.InteropServices.HandleRef, Int32, Int32, Int32, Int32 ByRef, System.Threading.NativeOverlapped*, System.Runtime.InteropServices.HandleRef) (IL_STUB_PInvoke) System.IO.FileSystemWatcher.Monitor(Byte[]) (Monitor) System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32, UInt32, System.Threading.NativeOverlapped*) (CompletionStatusChanged) System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32, UInt32, System.Threading.NativeOverlapped*) (CompletionStatusChanged) System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*) (PerformIOCompletionCallback)
How we can disable DMCC.config file checks if we dont need one?
Thanks, Alex.
|