I've tried to reproduce your bug... but i can't:
by me it works well, i've launched http_load several times and there's no locks:
[EMAIL PROTECTED] ~/essai_prg/http_load-12mar2006 $ ./http_load -parallel 100 -seconds 10 ./url
4165 fetches, 100 max parallel, 845495 bytes, in 10.0046 seconds
203 mean bytes/connection
416.308 fetches/sec, 84510.5 bytes/sec
msecs/connect: 0.466466 mean, 33.449 max, 0.05 min
msecs/first-response: 235.528 mean, 6545.72 max, 70.354 min
HTTP response codes:
code 200 -- 4165
My bug, is not related to server load, but it's related to compilation of many aspx page... My bug appears only if gamin is used!
Le jeudi 27 avril 2006 à 14:40 +0200, Robert Jordan a écrit :
_______________________________________________Hubert FONGARNAND wrote: > Hi Gonzalo, > > I've investigated on my "deadlock" problem. It seems that this problem > comes from GAMIN. > I explain: > > I'm running a big (more than 50 aspx, ascx) web application. If I run a > precompilation page (see the attached aspx.cs) > Mono, will compile about 20 pages, and will lock forever... > If you send a SIGQUIT to mod_mono_server you will obtain that some > thread do : > > - "" tid=0x0xb646bbb0 this=0x0x3893c0: > - in (wrapper managed-to-native) > System.IO.FAMWatcher:gamin_MonitorDirectory > (System.IO.FAMConnection&,string,System.IO.FAMRequest&,intptr) <0x4> > - in (wrapper managed-to-native) > System.IO.FAMWatcher:gamin_MonitorDirectory > (System.IO.FAMConnection&,string,System.IO.FAMRequest&,intptr) > <0xffffffbf> > - in System.IO.FAMWatcher:FAMMonitorDirectory > (System.IO.FAMConnection&,string,System.IO.FAMRequest&,intptr) <0x1f> > - in System.IO.FAMWatcher:StartMonitoringDirectory > (System.IO.FAMData,bool) <0x7d> > - in System.IO.FAMWatcher:StartDispatching > (System.IO.FileSystemWatcher) <0x192> > - in System.IO.FileSystemWatcher:Start () <0x17> > - in System.IO.FileSystemWatcher:set_EnableRaisingEvents (bool) <0x27> > - in (wrapper remoting-invoke-with-check) > System.IO.FileSystemWatcher:set_EnableRaisingEvents (bool) <0xffba2006> > > So the gamin_MonitorDirectory will never end and block all the other > thread... > The only way to force compilation contunation is to kill gam_server... > The compilation will continue, compile 5 page, and will block again!! > > I've tried to remove gamin from my linux... > and suprise!!! > > It work well, without gamin! > > Is there a way to tell mono, not to use gamin, for FAMWatcher, even if > gamin is installed? > My version of gamin, is the last one: 0.1.7 Set the env var MONO_MANAGED_WATCHER=1 BTW, can you reproduce this one? http://bugzilla.ximian.com/show_bug.cgi?id=78029 It's a similar (?) compilation issue that occurs even with the default managed watcher. Robert _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.
Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.
Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu.
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
