[Mono-bugs] [Bug 63862][Cri] New - XSP crash on every request

[bugzilla-daemon@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 bugzilla.ximian@rangie.com.

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

--- shadow/63862	2004-08-24 16:11:42.000000000 -0400
+++ shadow/63862.tmp.7552	2004-08-24 16:11:42.000000000 -0400
@@ -0,0 +1,117 @@
+Bug#: 63862
+Product: Mono: Runtime
+Version: unspecified
+OS: Solaris 8
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Critical
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: bugzilla.ximian@rangie.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: XSP crash on every request
+
+If this is shown to be a bug, I will happily raise a report in bugzilla, 
+but I think it is more likely that I have a problem with configuration. I 
+am installing mono on a SPARC running solaris 8. The version being 
+installed is the full set downloaded as mono reached version 1. I have 
+got round a number of problems so far, including the lack of aintl, the 
+lack of /dev/random and various other niggles. I have a working "Hello 
+World" running from the command line. XSP is compiled and installed, and 
+starts up without any visible problems. On startup, the following is seen 
+in the console :-
+
+bash-2.03# mono /usr/bin/xsp.exe --root
+/export/home/cdimages/mono_1/xsp-1.0/test/
+Adding applications '/:.'...
+Registering application:
+    Host:          any
+    Port:          any
+    Virtual path:  /
+    Physical path: /export/home/cdimages/mono_1/xsp-1.0/test
+Listening on port: 8080
+Listening on address: 0.0.0.0
+Root directory: /export/home/cdimages/mono_1/xsp-1.0/test
+Hit Return to stop the server.
+
+On the first request of a web page, the following error is received at 
+the browser, with no change made to the console window :-
+
+Server error in '/' application
+
+Description: Error processing request. 
+
+Error Message: HTTP 500. 
+
+Stack Trace: 
+ System.TypeInitializationException: An exception was thrown by the type 
+initializer for System.Web.Caching.Cache ---> System.OverflowException: 
+Resulting timespan is too big.
+ in <0x00470> System.TimeSpan:From (double,long)
+ in <0x00038> System.TimeSpan:FromDays (double)
+ in <0x0009c> System.Web.Caching.Cache:.cctor ()
+ --- End of inner exception stack trace ---
+
+ in (unmanaged) System.Web.Caching.Cache:.ctor ()
+ in <0x00034> System.Web.HttpRuntime:Init ()
+
+
+If the webpage is requested a second time, the browser sees :-
+
+Server error
+
+Your client sent a request that was not understood by this server. 
+
+And the console sees :-
+
+System.NullReferenceException: Object reference not set to an instance of 
+an object
+
+Server stack trace: 
+in <0x00094> System.Web.HttpRuntime:ProcessRequest 
+(System.Web.HttpWorkerRequest)
+in <0x00008> Mono.ASPNET.MonoWorkerRequest:ProcessRequest ()
+in <0x00074> Mono.ASPNET.BaseApplicationHost:ProcessRequest 
+(Mono.ASPNET.MonoWorkerRequest)
+in <0x00094> (wrapper remoting-invoke-with-check) 
+Mono.ASPNET.BaseApplicationHost:ProcessRequest 
+(Mono.ASPNET.MonoWorkerRequest)
+in <0x002a4> Mono.ASPNET.XSPApplicationHost:ProcessRequest 
+(int,string,int,string,int,string,string,string,string,string,byte
+[],string) in (unmanaged) (wrapper managed-to-native) 
+System.Runtime.Remoting.RemotingServices:InternalExecute 
+(System.Reflection.MonoMethod,object,object[],object[]&)
+in <0x00004> (wrapper managed-to-native) 
+System.Runtime.Remoting.RemotingServices:InternalExecute 
+(System.Reflection.MonoMethod,object,object[],object[]&)
+in <0x001f8> 
+System.Runtime.Remoting.RemotingServices:InternalExecuteMessage 
+(System.MarshalByRefObject,System.Runtime.Remoting.Messaging.IMethodCallMe
+ssage)
+
+Exception rethrown at [0]: 
+
+in <0x00a2c> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
+(System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messagi
+ng.IMessage,System.Exception&,object[]&)
+
+
+The code of the page being requested in this example is pure html, no 
+asp, although the same error is received for more complex pages :-
+
+<html>
+<body>
+Some words here to show that xsp is able to interpret a static html page
+</body>
+</html>
+
+This happens every time.
+
+If anyone is able to help out, I would be extremely grateful. I have 
+searched google and the archives, but to no avail as yet. If there is any 
+other information I can provide, please ask.