[Mono-bugs] [Bug 82840][Nor] Changed - Unhandled exception changes make xsp2 quit

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by dna at informatik.uni-kiel.de.

http://bugzilla.ximian.com/show_bug.cgi?id=82840

--- shadow/82840	2007-09-13 19:34:57.000000000 -0400
+++ shadow/82840.tmp.1577	2007-09-14 04:14:29.000000000 -0400
@@ -45,6 +45,25 @@
 This will give you a chance to print the exception (inside the
 handler).
 
 ------- Additional Comments From mhabersack at novell.com  2007-09-13 19:34 -------
 Maybe this article will shed some light -
 http://www.eggheadcafe.com/articles/20060305.asp
+
+------- Additional Comments From dna at informatik.uni-kiel.de  2007-09-14 04:14 -------
+First i tested the:
+AppDomain.CurrentDomain.UnhandledException += new
+UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);
+
+handler in Application_Start of my Global.asax. The handler loggs the
+exception into log4net and prints it to the console.
+But xsp2 quits without any message.
+
+Then i tested the UnhandledExceptionHttpModule solution. Same result.
+
+I enabled heavy logging in my application and it turns out, that it
+happens every time i'm using:
+Activator.CreateInstance("Npgsql", "Npgsql.NpgsqlConnection").Unwrap()
+
+(the latest logentry is short before that instruction)
+
+As far as i can say i dont had this problem on tuesday with r85628.