[Mono-bugs] [Bug 70703][Maj] New - RemotingException on Windows when using TcpChannel

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 20 Dec 2004 15:13:35 -0500 (EST)


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 sebastien.robitaille@croesus.com.

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

--- shadow/70703	2004-12-20 15:13:35.000000000 -0500
+++ shadow/70703.tmp.16246	2004-12-20 15:13:35.000000000 -0500
@@ -0,0 +1,67 @@
+Bug#: 70703
+Product: Mono: Class Libraries
+Version: 1.0
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: CORLIB
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastien.robitaille@croesus.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: RemotingException on Windows when using TcpChannel
+
+Description of Problem:
+
+NOTE: This bug is a follow-up of bug #70337 and #70702
+
+When using the test case provided for bug #70337 on Windows, there is a 
+RemotingException thrown after a few seconds of execution.
+This problem can be reproduced only on Windows.
+
+
+Unhandled Exception: System.Runtime.Remoting.RemotingException: Unknown 
+response
+ message from server
+
+Server stack trace:
+in <0x001d2> 
+System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink:Process
+Message 
+(System.Runtime.Remoting.Messaging.IMessage,System.Runtime.Remoting.Chan
+nels.ITransportHeaders,System.IO.Stream,System.Runtime.Remoting.Channels.I
+Transp
+ortHeaders&,System.IO.Stream&)
+in <0x002bf> 
+System.Runtime.Remoting.Channels.BinaryClientFormatterSink:SyncProc
+essMessage (System.Runtime.Remoting.Messaging.IMessage)
+
+
+Exception rethrown at [0]:
+
+in <0x005a4> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke 
+(System.Run
+time.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage
+,Syste
+m.Exception&,object[]&)
+
+Steps to reproduce the problem:
+1. Run the test case on Windows.
+
+Actual Results:
+Exception thrown.
+
+Expected Results:
+No exception.
+
+How often does this happen? 
+Always (You must let the client and server applications run for a few 
+seconds before the exception to be thrown).
+
+Additional Information:
+This problem can be reproduced only on Windows.