Re: [Mono-dev] BasicHttpBinding issues
Hello, This is sort of a correct list (mono-list may be better unless mono development is involved). I have no idea on from which this list addition occurs. This might not happen in the latest git head or daily builds (but I doubt that). If you can provide the runnable example code, I can test it on the latest code. Atsushi Eno On 2010/08/12 12:21, Matthew Fanto wrote: Forgive me if this is the wrong list. I checked the descriptions of the various lists, and this one seemed to be the most relevant, as I'm seeing a difference between running under .NET 3.5 and Mono 2.6.7. I am attempting to create a WCF service. I've been unable to get either NetTcpBinding or BasicHttpBinding working, yet both work fine if I run under .NET. Running under Mono 2.6.7 on Windows 7 x64, I occasionally get an exception Exception during finishing channel acceptance with a System.IndexOutofRangeException: Array index is out of range. This happens half the time that I run the service. I never get these exceptions if I am running under .NET. The end of the stack trace looks like: at (wrapper stelemref) object:stelemref (object,intptr,object) at System.Collections.Generic.List`1[System.ServiceModel.Channels.IChannel].Add (IChannel item) [0x0001a] in C:\cygwin\tmp\monobuild\build\BUILD\mono-2.6.7\mcs\class\corlib\System.Collections.Generic\List.cs:89 at System.ServiceModel.Dispatcher.ListenerLoopManager.ChannelAccepted (IChannel ch) [0x0004c] in C:\cygwin\tmp\monobuild\build\BUILD\mono-2.6.7\mcs\class\System.ServiceModel\System.ServiceModel.Dispatcher\ChannelDispatcher.cs:499 at System.ServiceModel.Dispatcher.ListenerLoopManager+CreateAcceptorc__AnonStorey1C`1[System.ServiceModel.Channels.IReplyChannel].m__1F (IAsyncResult result) [0x0] in C:\cygwin\tmp\monobuild\build\BUILD\mono-2.6.7\mcs\class\System.ServiceModel\System.ServiceModel.Dispatcher\ChannelDispatcher.cs:373 I can provide the full stack trace if needed. When the service does start, any clients that attempt to connect get an Error 400. I create the ServiceHost with: var host = new ServiceHost(typeof(TestService)); host.AddServiceEndpoint(typeof(ITestService), new BasicHttpBinding(), http://127.0.0.1:/test;); host.Open(); I have also attempted to run the service under OpenSuSE 11.3, and get the same Error 400. Everything works fine under .NET 3.5 however. I have set all the buffer sizes to their max value. I'd appreciate any help or direction (or if I should be sending this to another list). Best, Matt ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] BasicHttpBinding issues
On Thu, Aug 12, 2010 at 2:06 AM, Atsushi Eno atsushi...@veritas-vos-liberabit.com wrote: I have no idea on from which this list addition occurs. This might not happen in the latest git head or daily builds (but I doubt that). If you can provide the runnable example code, I can test it on the latest code. I might have been quick with my initial email before checking everything. I also apologize for being vague on details, but everytime it ran, I had different results. Nothing was predictable. I've played with this down further and it seems to be caused by Mono Tools for Visual Studio. If I run the application from cmd.exe with mono.exe test.exe, the WCF service listens, and responds to requests as it should. If I run from within Visual Studio, I am unable to get anything to run. If I use Run in Mono, I get an error that the assembly is too large. Using Debug in Mono, sometimes the service starts but rejects any request. Other times, the application crashes with unhandled exceptions. Also, if I kill the debugger, mono.exe still hangs and does not terminate. I have to manually terminate it. cmd.exe runs as the same privileges as Visual Studio. Best, Matt ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] BasicHttpBinding issues
Hello, For random results, it is rather likely that 2.6 HttpTransport listener confuses between the contract service endpoint and WSDL/debug endpoint (i.e. WSDL endpoint could try to process the contract messages, or the contract endpoint may try to process WSDL requests). Explicitly disabling ServiceDebugBehavior and ServiceMetadataBehavior (serviceDebug and serviceMetadata in config) might fix this specific issue. And if you still gets failures occasionally (or consistently), it may be time to have some doubts on Tools for VS. Anyways you can feel free to send me your code and try it at my side if you want :) Atsushi Eno On 2010/08/12 15:17, Matthew Fanto wrote: On Thu, Aug 12, 2010 at 2:06 AM, Atsushi Eno atsushi...@veritas-vos-liberabit.com mailto:atsushi...@veritas-vos-liberabit.com wrote: I have no idea on from which this list addition occurs. This might not happen in the latest git head or daily builds (but I doubt that). If you can provide the runnable example code, I can test it on the latest code. I might have been quick with my initial email before checking everything. I also apologize for being vague on details, but everytime it ran, I had different results. Nothing was predictable. I've played with this down further and it seems to be caused by Mono Tools for Visual Studio. If I run the application from cmd.exe with mono.exe test.exe, the WCF service listens, and responds to requests as it should. If I run from within Visual Studio, I am unable to get anything to run. If I use Run in Mono, I get an error that the assembly is too large. Using Debug in Mono, sometimes the service starts but rejects any request. Other times, the application crashes with unhandled exceptions. Also, if I kill the debugger, mono.exe still hangs and does not terminate. I have to manually terminate it. cmd.exe runs as the same privileges as Visual Studio. Best, Matt ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] BasicHttpBinding issues
Forgive me if this is the wrong list. I checked the descriptions of the various lists, and this one seemed to be the most relevant, as I'm seeing a difference between running under .NET 3.5 and Mono 2.6.7. I am attempting to create a WCF service. I've been unable to get either NetTcpBinding or BasicHttpBinding working, yet both work fine if I run under .NET. Running under Mono 2.6.7 on Windows 7 x64, I occasionally get an exception Exception during finishing channel acceptance with a System.IndexOutofRangeException: Array index is out of range. This happens half the time that I run the service. I never get these exceptions if I am running under .NET. The end of the stack trace looks like: at (wrapper stelemref) object:stelemref (object,intptr,object) at System.Collections.Generic.List`1[System.ServiceModel.Channels.IChannel].Add (IChannel item) [0x0001a] in C:\cygwin\tmp\monobuild\build\BUILD\mono-2.6.7\mcs\class\corlib\System.Collections.Generic\List.cs:89 at System.ServiceModel.Dispatcher.ListenerLoopManager.ChannelAccepted (IChannel ch) [0x0004c] in C:\cygwin\tmp\monobuild\build\BUILD\mono-2.6.7\mcs\class\System.ServiceModel\System.ServiceModel.Dispatcher\ChannelDispatcher.cs:499 at System.ServiceModel.Dispatcher.ListenerLoopManager+CreateAcceptorc__AnonStorey1C`1[System.ServiceModel.Channels.IReplyChannel].m__1F (IAsyncResult result) [0x0] in C:\cygwin\tmp\monobuild\build\BUILD\mono-2.6.7\mcs\class\System.ServiceModel\System.ServiceModel.Dispatcher\ChannelDispatcher.cs:373 I can provide the full stack trace if needed. When the service does start, any clients that attempt to connect get an Error 400. I create the ServiceHost with: var host = new ServiceHost(typeof(TestService)); host.AddServiceEndpoint(typeof(ITestService), new BasicHttpBinding(), http://127.0.0.1:/test;); host.Open(); I have also attempted to run the service under OpenSuSE 11.3, and get the same Error 400. Everything works fine under .NET 3.5 however. I have set all the buffer sizes to their max value. I'd appreciate any help or direction (or if I should be sending this to another list). Best, Matt ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
