[Mono-list] mod_mono failures
Gonzalo Paniagua Javier
gonzalo.reply.to.the.list.iam.subscribed@ximian.com
Fri, 08 Oct 2004 20:06:54 +0200
On Fri, 2004-10-08 at 19:36, CJ Collier wrote:
> Hey all,
>
> I don't know where mod_mono discussion goes, so I'm going to bring it
> here. Please correct me if I'm in the wrong place.
mono-list is the right place.
>
> I spent some time putting together a test of mod_mono on my apache2
> server yesterday:
>
> http://www.colliertech.com/demo/index.aspx
>
> As you can tell, it didn't go so well.
>
> Here's some debugging info. I ran apache2 -X and then hit that page:
>
> $ sudo apache2 -X
> mod-mono-server
> Adding applications '/demo:/usr/local/share/doc/xsp/test'...
> Registering application:
> Host: any
> Port: any
> Virtual path: /demo/
> Physical path: /usr/local/share/doc/xsp/test
> Listening on: /tmp/mod_mono_server
> Root directory: /
> System.ArgumentOutOfRangeException: Abnormal string size.
> Parameter name: size
> in <0x00065> Mono.ASPNET.ModMonoRequest:ReadString ()
> in <0x00050> (wrapper remoting-invoke-with-check)
> Mono.ASPNET.ModMonoRequest:ReadString ()
> in <0x000a9> Mono.ASPNET.ModMonoRequest:GetInitialData ()
> in <0x0004f> (wrapper remoting-invoke-with-check)
> Mono.ASPNET.ModMonoRequest:GetInitialData ()
> in <0x000ef> Mono.ASPNET.ModMonoRequest:.ctor
> (System.Net.Sockets.NetworkStream)in <0x00056> (wrapper remoting-invoke-
> with-check) Mono.ASPNET.ModMonoRequest:.ctor
> (System.Net.Sockets.NetworkStream)
> in <0x00034> Mono.ASPNET.RequestReader:.ctor
> (System.Net.Sockets.NetworkStream)
> in <0x00077> Mono.ASPNET.ModMonoWorker:Run (object)
>
> I've attached a copy of my /etc/apache2/mods-enabled/mod_mono.conf file.
>
> I installed xsp and mod_mono from anon cvs.
>
> xsp's ChangeLog's cvs log says that its release is 1.83
> mod_mono's ChangeLog's cvs log says that its release is 1.92
>
> I ran mod_mono's ./configure with --prefix=/usr
> I ran xsp's ./configure without a --prefix
>
> Any idea what might be throwing this exception?
No idea, but that error would happen if mod_mono and mod-mono-server are
not compatible, but that does not happen with the versions you report,
as they are what CVS has now and are working fine here.
-Gonzalo