[Mono-dev] DeadLock Problem in ASP.NET (GAMIN)

[Hubert FONGARNAND]

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

I'will try to do a test case with many aspx files, to show you the
problem!

Thanks in advance

Le mardi 25 avril 2006 à 18:03 -0700, Gonzalo Paniagua Javier a écrit :

> On Tue, 2006-04-25 at 18:25 +0200, Hubert FONGARNAND wrote:
> > Hi Gonzalo,
> > 
> > It seems that i've another deadlock problem,
> > but it's very hard to reproduce exactly
> > I've send a SIGQUIT to mod_mono_server to do a thread dump :
> 
> Can you provide more data here? Specifically, the @Page or @Control
> directive for the page/control that is being compiled and anything else
> that helps reproducing the problem.
> 
> -Gonzalo
> 
_______________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060427/880ce0f3/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PreCompile.aspx.cs
Type: text/x-csharp
Size: 6070 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20060427/880ce0f3/attachment.bin