Hi, Threads WAPI handle leaks has always caused problems with ASP.NET and MONO. In the past, there has been many bugs related to this problem... Now, we use mono to power our intranet (more than 4000 users...).
I'm monitoring the number of wapi handles using mono --wapi=hps | wc -l During the day, the number of WAPI handles keeps stable. It seems that the GC collect them correctly... but during the night when our intranet is inactive the number of WAPI handles grows... and sometimes reach the limit of 4096... And crashes the mod-mono-server's... Two question : -> why the number of WAPI handles grows... when there's no activity on the site (if the ASP.NET application has been very busy during the day... it will grows faster during the night) ? -> don't you thing that a 4096 limit for WAPI handles is too small for big production servers? (on windows the number of handles is often >6000)? Thanks for helping me fixing this issue Hubert FONGARNAND I've a workaround: I use my monitoring system to send a request (that do a GC.Collect()) on each ASP.NET apps every 5 minutes Some graphs (without the 5 minutes ping)
<<attachment: chart.php.png>>
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
