[Mono-devel-list] Read failure with XSP on Windows
kevin.flanagan at bom.co.uk
Mon Apr 18 13:29:31 EDT 2005
Well - hard to know if that is a factor. If I use Opera instead of IE, I get
just the same 'Read failure' problem. But if I use Firefox ... I get a
at all ... but they do if I point Firefox at the same app served by IIS
instead of XSP ... But unless Opera sends the same extra linefeed as IE, I'm
guessing the 'Read failure' is a different problem. Thanks though.
De: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com]En nombre de Curtis Wensley
Enviado el: 13 April 2005 20:58
Para: mono-devel-list at lists.ximian.com
Asunto: Re: [Mono-devel-list] Read failure with XSP on Windows
This could be related to this bug I submitted:
XSP didn't account for the extra linefeed that IE sends. If you use
firefox, everything should work fine (if this is indeed the problem).
This is now fixed, and should be in 1.1.5 (by looking at the date it was
fixed - march 16th)
Hope this helps!,
On Wednesday 13 April 2005 08:24, Kevin Flanagan wrote:
> Hello - I've installed Mono 1.1.4 on XP Pro - am writing an ASP.NET app
> run under .NET and Mono, so it's very helpful to be able to test both on
> the same OS. The app (quite simple at present) basically runs fine under
> Mono, after a couple of tweaks ... in fact, I'm likely to be joining the
> ranks of those with nothing but praise for Mono. The only problem I
> solve is getting 'Read failure' on *almost* every page postback (running
> XSP and using IE6 on the same XP machine). I've seen this referred to
> elsewhere (e.g.
> http://www.webtropy.com/articles/art16-mono.asp?MONO%20for%20Linux) but
> on this list, nor with any suggested solution.
> The results in the browser look like this:
> Server error in '/' application
> Description: Error processing request.
> Error Message: HTTP 500.
> Stack Trace: System.IO.IOException: Read failure
> Server stack trace:
> in <0x000b8> System.Net.Sockets.NetworkStream:Read (byte,int,int)
> in <0x00017> Mono.ASPNET.XSPWorker:Read (byte,int,int)
> in <0x0012e> Mono.ASPNET.BaseRequestBroker:Read (int,int,byte&)
> in <0x00131> (wrapper xdomain-dispatch)
> Exception rethrown at :
> ---> System.Net.Sockets.SocketException: Operation on non-blocking
> would blockin <0x0006b> System.Net.Sockets.Socket:Receive_nochecks
> in <0x0005b> System.Net.Sockets.Socket:Receive
> in <0x0007b> System.Net.Sockets.NetworkStream:Read (byte,int,int)
> --- End of inner exception stack trace ---
> in <0x00211> (wrapper xdomain-invoke) Mono.ASPNET.BaseRequestBroker:Read
> in <0x0004b> (wrapper remoting-invoke-with-check)
> Mono.ASPNET.BaseRequestBroker:Read (int,int,byte&)
> in <0x000a5> Mono.ASPNET.XSPWorkerRequest:ReadInput (byte,int,int)
> in <0x0001f> Mono.ASPNET.XSPWorkerRequest:ReadEntityBody (byte,int)
> in <0x00252> System.Web.HttpRequest:GetRawContent ()
> in <0x0005c> System.Web.HttpRequest:ParseFormData ()
> in <0x00012> System.Web.HttpRequest:get_Form ()
> in <0x00062> System.Web.UI.Page:DeterminePostBackMode ()
> in <0x0001a> System.Web.UI.Page:InternalProcessRequest ()
> in <0x00095> System.Web.UI.Page:ProcessRequest (System.Web.HttpContext)
> in <0x00225> ExecuteHandlerState:Execute ()
> in <0x00071> StateMachine:ExecuteState
> Can anyone suggest a solution?
> Thanks in advance for any help.
> Kevin Flanagan.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list