[Mono-list] Unstable XSP 2.4 RC1

[Pedro Santos]

Today I got mono from svn and compiled & installed branch mono-2-4.
I am still testing to see it this problem is fixed, but I run with a
problem that I got on mono 2.2 that was fixed on 2.4.
The problem was that the assembly's CodeBase was wrong, was the same
as the Location. This today's snapshot I got that error again.

The bug was:
http://www.mail-archive.com/mono-bugs@lists.ximian.com/msg57369.html

And I'm running:

# mono --version
Mono JIT compiler version 2.4 (/branches/mono-2-4/mono r128706 Thu Mar
 5 17:07:32 WET 2009)

# ps ax | grep mono
30792 ?        Sl     0:12 /usr/local/mono/mono-2.4_svn//bin/mono
/usr/local/mono/mono-2.4_svn//lib/mono/2.0/fastcgi-mono-server2.exe

Is this a regression or some problem with my configurations?

Thank you.


On Wed, Mar 4, 2009 at 7:10 PM, Marek Habersack <grendel at twistedcode.net> wrote:
> On Wed, 2009-03-04 at 17:44 +0000, Pedro Santos wrote:
>> Hello,
> Hello,
>
>>
>> We have several applications running on mono on a beta stage. We
>> recently migrated from win to mono and we have the following setup:
>>
>> » nginx + mono fastcgi server
>> » only one instance of fastcgi-mono-server2 but with several applications (4)
> [snip]
>> After having this error for the first time we start to get it on
>> several pages, but if we restart fastcgi-mono-server2 it starts to
>> work ok. After some time the error comes again.
>>
>> Is there anything else I can do to help fixing this?
>>
>> I have gathered two related exceptions from our logs:
>>
>> --------- ERROR --------------
>> System.Web.Compilation.CompilationException: CS0006: cannot find
>> metadata file `/tmp/root-temp-aspnet-0/6f3f8f0/App_global.asax.f105942.dll'
> [snip]
> All of the issues are most likely caused by a race condition in
> system.web's application domain shutdown code. Namely, just before
> AppDomain.Unload is called, the dynamic base directory (where the .dll
> and code files created while compiling the .as?x are kept) is cleared
> which may, under certain time conditions, cause the build manger (and
> possibly other code) to fail because the files it expected to find are
> no longer there. The commits to svn trunk, revision 128602, and to the
> 2.4 branch, revision 128603 should fix that.
>
> best regards,
>
> marek
>
>



-- 
Pedro Santos
Home - http://psantos.zi-yu.com
Work - http://www.pdmfc.com
The future - http://www.orionsbelt.eu