[Mono-bugs] [Bug 647990] New random crashes, timeouts and bad performance in asp.net with 2.8.x branch

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=647990

https://bugzilla.novell.com/show_bug.cgi?id=647990#c3


--- Comment #3 from Marek Habersack <mhabersack at novell.com> 2010-10-20 15:03:24 CEST ---
(In reply to comment #2)
> Sorry about the severity. I interpreted it literally: crashing, hanging...
> 
> - The main problem is I not able to get any more info about the bug. If I could
> I would look at the source in order to find the problem.
> But there is no HTTP 500 stack trace, it's not the tipical asp.net 500 error
> with some info from the mono runtime. It's the default apache 500 error.
> "contact the administrator and look at the log files"
> 
> - I already compiled mod_mono with --mono-debug, and enabled LogLevel debug in
It's --enable-debug, passed to mod_mono's configure script

> httpd.conf and MonoDebug myserver true in the application config. But the only
> info I get is that:
>  [error] (104)Connection reset by peer: read_data failed
>  [error] Command stream corrupted, last command was -1
Which means your mod_mono is not compiled with --enable-debug (or you load a
different module, not the one you compiled with --enable-debug)

> I compiled mod_mono and mod-mono-server from the same version (2.8 from the
> webpage first, and git clones downloaded at same time later).
> 
> I also tried changing the versions of mod_mono and xp (2.6.7 versions agains
> 2.8 mono) But only reinstalling mono 2.6.7 fixed the problem.
> 
> Could you help me? what else can I enable to find the source of the bug?
There's not nearly enough info to solve this at this point. You might want to
check if the file descriptor limit isn't hit (it defaults to 1024), you can run
mono with --trace=dummy to see what exceptions are thrown and hidden from you,
you can check when the connection timeout happens - on connect, on write, on
read? Read http://mono-project.com/Debugging#Debugging_Managed_Lock_Deadlocks
and make sure there are no deadlocks.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.