[Mono-bugs] [Bug 78696][Maj] New - Bug on remothing

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Jun 23 14:44:15 EDT 2006


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 albertoavila at gmail.com.

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

--- shadow/78696	2006-06-23 14:44:15.000000000 -0400
+++ shadow/78696.tmp.2530	2006-06-23 14:44:15.000000000 -0400
@@ -0,0 +1,89 @@
+Bug#: 78696
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: albertoavila at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Bug on remothing
+
+Description of Problem:
+When runing a remothing service on mono (1.1.7.1, may happend on others
+version, i haven't tested it) in windows xp (may occur on linux, i haven't
+tested it) the client gets a exception when calling it, if the service is
+run with .net everything works ok (same binary)
+
+
+Steps to reproduce the problem:
+1. Take de code from http://monoport.com/296
+2. Put IServicio on IServicio.cs and User on User.cs and compile it as
+Common.dll mcs IServicio.cs User.cs -target:library -out:Common.dll
+3. Put Server on Server.cs and compile it making a reference to Common.dll
+mcs Server.cs -r:Common.dll,System.Runtime.Remoting.dll -out:Server.exe
+4. Put Cliente on Client.cs and compile it making a reference to Common.dll
+mcs Client.cs -r:Common.dll,System.Runtime.Remoting.dll -out:Client.exe
+5. Run server on mono: mono Server.exe
+6. Run client on mono or .net: Mono Client.exe
+Actual Results:
+When runing the client on mono you get the following exception:
+
+Unhandled Exception:
+System.Runtime.Serialization.SerializationException: There are some
+fixups that refer to objects that have not been registered
+
+Server stack trace:
+
+
+Exception rethrown at [0]:
+
+in <0x006d1> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
+System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg,
+System.Exception exc, System.Object[] out_args)
+
+But if instead you run the client on .net you got:
+
+Unhandled Exception: System.Net.WebException: The remote server
+returned an error: (400) Bad Request.
+
+Server stack trace:
+  at
+System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessResponseException(WebException
+webException, HttpWebResponse& response)
+  at
+System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage
+msg, ITransportHeaders requestHeaders, Stream requestStream,
+ITransportHeaders& responseHeaders, Stream& responseStream)
+  at
+System.Runtime.Remoting.Channels.SoapClientFormatterSink.SyncProcessMessage(IMessage
+msg)
+
+Exception rethrown at [0]:
+  at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
+reqMsg, IMessage retMsg)
+  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
+msgData, Int32 type)
+  at Common.IServicio.getPeticionesWeb(String Usuario, String Llave1,
+String Modulo, String NReporte, String Fechas)
+  at Cliente.Cliente.Main(String[] args)
+
+
+***IF YOU RUN THE SERVER WITH .NET THE CLIENT WORKS RUNNING ON MONO OR
+.NET, THIS IS A PROBLEM OF THE MONO REMOTING PROVIDER, NOT THE CLIENT***
+
+
+Expected Results:
+
+The test case should work like it works running the server on .NET
+
+
+How often does this happen? 
+Always


More information about the mono-bugs mailing list