[Mono-bugs] [Bug 472732] mod-mono spawns many process and fails to respond when using AutoRestartMode

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Feb 16 15:43:49 EST 2009


User mhabersack at novell.com added comment

Marek Habersack <mhabersack at novell.com> changed:

           What    |Removed                     |Added
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #21 from Marek Habersack <mhabersack at novell.com>  2009-02-16 13:43:44 MST ---
So, it seems I was partially correct in the analysis given above, with the
exception that the FD starvation was produced by mod_mono/mod-mono-server
itself. The real source of the bug, discovered by Zoltan Varga, was that some
apache versions appear to block certain signals used by the Mono runtime and,
more importantly, by its garbage collector. As the result, mod_mono was
correctly starting new backend copies but, having previously removed the unix
socket file used for communications with them, it relied upon the new backend
to create that file - which never happened. The reason why it never happened
was that as soon as the GC kicked in within the child process it blocked
waiting on a semaphore to never wake up as delivery of the signals mentioned
above was impossible.
The issue has been fixed in svn trunk, revision 127064 and in the 2.4 branch,
revision 127063

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

More information about the mono-bugs mailing list