[Mono-bugs] [Bug 372220] New: mod-mono-server always crashes when using --port
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Wed Mar 19 00:46:06 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=372220
Summary: mod-mono-server always crashes when using --port
Product: Mono: Class Libraries
Version: 1.2.5
Platform: All
OS/Version: Windows XP
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Sys.Web
AssignedTo: mhabersack at novell.com
ReportedBy: dcohenp at eduinnova.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Created an attachment (id=202836)
--> (https://bugzilla.novell.com/attachment.cgi?id=202836)
fix for Mono.WebServer.Apache/main.cs r98568
Ever since mono 1.2.5 (still valid in SVN trunk), mod_mono+Apache 2.2 hosted
applications silently stop working in Windows (using Windows mod_mono from
http://anmar.eu.org/mono/mod_mono/).
Symptom: any application which mod_mono is registered to execute makes Apache
return a 500 server error.
Upon closer examination, and executing mod-mono-server.exe by hand with the
same parameters used by mod_mono to launch it, realized that it is always
throwing a FormatException.
Looking at the source (xsp/src/Mono.WebServer.Apache/main.cs), the problem
seems simple: when all the initial checks have succeeded, and the server is
about to start listening, it prints an informational Console message which is
wrongly formatted (closing brace missing). Simply adding the brace brings
everything back to normal.
This only happens when using TCP mode (the --port parameter), used by default
in Windows, which apparently few of us are using, so this went by undetected
for a while.
Steps to Reproduce: Run _any_ ASP.NET 1.0 app under Windows XP/Apache 2.2/mono
1.2.5/mod_mono-win32 r89283 (from http://anmar.eu.org/mono/mod_mono).
Actual Result: ALWAYS get a 500 server error, with no further information in
the Apache error logs.
--
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